Default Component Exception Strategy being thrown on wrong component

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: To be reviewed To be reviewed
  • Resolution: Won't Fix or Usage Issue
  • Affects Version/s: 1.4.3
  • Fix Version/s: None
  • Component/s: Core: Exception Handling
  • Labels:
    None
  • Environment:

    Windows Server 2003, Java 1.5

  • User impact:
    Medium
  • Configuration:
    Hide

    <mule-descriptor name="FileDownloader" implementation="org.mule.components.simple.BridgeComponent">
    <inbound-router>
    <endpoint address="ftp://user:pass@ftp.ftpsite.com/folder">
    <filter pattern="*.xls" className="org.mule.providers.file.filters.FilenameWildcardFilter"/>
    <properties>
    <property name="pollingFrequency" value="300000"/>
    </properties>
    </endpoint>
    </inbound-router>
    <outbound-router>
    <router className="org.mule.routing.outbound.OutboundPassThroughRouter">
    <endpoint address="file:///f:/files/inbox">
    <properties>
    <property name="outputPattern" value="${ORIGINALNAME}"/>
    </properties>
    </endpoint>
    </router>
    </outbound-router>
    </mule-descriptor>

    <mule-descriptor name="FileParser" implementation="com.novus.test.templates.TestFile">
    <inbound-router>
    <endpoint connector="inputFolder" address="file:///f:/files/inbox">
    <filter pattern="*.xls" className="org.mule.providers.file.filters.FilenameWildcardFilter"/>
    <properties>
    <property name="pollingFrequency" value="20000"/>
    <property name="moveToDirectory" value="f:/files/archive"/>
    </properties>
    </endpoint>
    </inbound-router>
    <pooling-profile maxActive="5" maxIdle="10"
    initialisationPolicy="INITIALISE_ALL"
    exhaustedAction="WHEN_EXHAUSTED_WAIT" maxWait="-1"/>
    <exception-strategy className="org.mule.impl.DefaultComponentExceptionStrategy">
    <endpoint address="file:///f:/files/errors">
    <properties>
    <property name="binary" value="true"/>
    <property name="outputPattern" value="${ORIGINALNAME}"/>
    </properties>
    </endpoint>
    </exception-strategy>
    </mule-descriptor>

    Show
    <mule-descriptor name="FileDownloader" implementation="org.mule.components.simple.BridgeComponent"> <inbound-router> <endpoint address="ftp://user:pass@ftp.ftpsite.com/folder"> <filter pattern="*.xls" className="org.mule.providers.file.filters.FilenameWildcardFilter"/> <properties> <property name="pollingFrequency" value="300000"/> </properties> </endpoint> </inbound-router> <outbound-router> <router className="org.mule.routing.outbound.OutboundPassThroughRouter"> <endpoint address="file:///f:/files/inbox"> <properties> <property name="outputPattern" value="${ORIGINALNAME}"/> </properties> </endpoint> </router> </outbound-router> </mule-descriptor> <mule-descriptor name="FileParser" implementation="com.novus.test.templates.TestFile"> <inbound-router> <endpoint connector="inputFolder" address="file:///f:/files/inbox"> <filter pattern="*.xls" className="org.mule.providers.file.filters.FilenameWildcardFilter"/> <properties> <property name="pollingFrequency" value="20000"/> <property name="moveToDirectory" value="f:/files/archive"/> </properties> </endpoint> </inbound-router> <pooling-profile maxActive="5" maxIdle="10" initialisationPolicy="INITIALISE_ALL" exhaustedAction="WHEN_EXHAUSTED_WAIT" maxWait="-1"/> <exception-strategy className="org.mule.impl.DefaultComponentExceptionStrategy"> <endpoint address="file:///f:/files/errors"> <properties> <property name="binary" value="true"/> <property name="outputPattern" value="${ORIGINALNAME}"/> </properties> </endpoint> </exception-strategy> </mule-descriptor>
  • Log Output:
    Hide
    INFO 2008-03-13 11:59:16,866 [connector.ftp.0.receiver.1] org.mule.impl.DefaultExceptionStrategy: There is no current event available, routing Null message with the exception
    ERROR 2008-03-13 11:59:16,866 [connector.ftp.0.receiver.1] org.mule.impl.DefaultExceptionStrategy: Caught exception in Exception Strategy: null
    java.lang.NullPointerException
                    at org.mule.providers.ftp.FtpMessageReceiver.listFiles(FtpMessageReceiver.java:123)
                    at org.mule.providers.ftp.FtpMessageReceiver.poll(FtpMessageReceiver.java:72)
                    at org.mule.providers.PollingReceiverWorker.run(PollingReceiverWorker.java:47)
                    at org.mule.impl.work.WorkerContext.run(WorkerContext.java:310)
                    at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:987)
                    at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:528)
                    at java.lang.Thread.run(Unknown Source)
    Show
    INFO 2008-03-13 11:59:16,866 [connector.ftp.0.receiver.1] org.mule.impl.DefaultExceptionStrategy: There is no current event available, routing Null message with the exception ERROR 2008-03-13 11:59:16,866 [connector.ftp.0.receiver.1] org.mule.impl.DefaultExceptionStrategy: Caught exception in Exception Strategy: null java.lang.NullPointerException                 at org.mule.providers.ftp.FtpMessageReceiver.listFiles(FtpMessageReceiver.java:123)                 at org.mule.providers.ftp.FtpMessageReceiver.poll(FtpMessageReceiver.java:72)                 at org.mule.providers.PollingReceiverWorker.run(PollingReceiverWorker.java:47)                 at org.mule.impl.work.WorkerContext.run(WorkerContext.java:310)                 at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:987)                 at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:528)                 at java.lang.Thread.run(Unknown Source)
  • Similar Issues:
    None

Description

Here is the email I submitted to the user list where Ross asked me to raise this as a bug:
------------------------------------------------------
I recently added two new components to my Mule deployment. The first component monitors an FTP folder and downloads files to a local directory as they become available. The second component monitors that local directory for new files and extracts the necessary information from them. One thing I did that I hadn't done before was add the <exception-strategy> handler for the second component. Unfortunately, what happens now is that I get an error in my log file whenever there is no file to download from the FTP server.

Two questions:

  • What do I need to do to fix the error from being thrown when there is no file to process?
  • Why is the error occurring on the FileDownloader component when I added the <exception-strategy> handler to the FileParser component? I can tell this because the error messages in the log file are in 5 minute increments; that's the same polling frequency as the FileDownloader inbound endpoint.

Activity

Hide
Permalink
Mike Schilling added a comment -

Sorry, Mule 1 is no longer supported. If you can reproduce this in a supported version, please enter a new issue.

Show
Mike Schilling added a comment - Sorry, Mule 1 is no longer supported. If you can reproduce this in a supported version, please enter a new issue.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: