[02-05 10:17:55] ERROR DefaultExceptionStrategy [connector.tcp.0.receiver.2]: Caught exception in Exception Strategy: null
java.lang.InterruptedException
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:429)
at edu.emory.mathcs.backport.java.util.concurrent.CountDownLatch.await(CountDownLatch.java:178)
at org.mule.providers.tcp.TcpMessageReceiver$TcpStreamWorker.handleResults(TcpMessageReceiver.java:408)
at org.mule.providers.AbstractReceiverWorker.doRun(AbstractReceiverWorker.java:125)
at org.mule.providers.AbstractReceiverResourceWorker.doRun(AbstractReceiverResourceWorker.java:50)
at org.mule.providers.AbstractReceiverWorker.run(AbstractReceiverWorker.java:60)
at org.mule.impl.work.WorkerContext.run(WorkerContext.java:310)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575)
at java.lang.Thread.run(Thread.java:534)
[02-05 10:17:55] ERROR DefaultExceptionStrategy [connector.tcp.0.receiver.2]:
********************************************************************************
Message : Cannot route event as component "bridge2" is stopped. Component that caused exception is: bridge2. Message payload is of type: CloseCountDownInputStream
Type : org.mule.umo.ComponentException
Code : MULE_ERROR-79999
JavaDoc :
http://mule.mulesource.org/docs/apidocs/org/mule/umo/ComponentException.html
Payload :
org.mule.impl.model.streaming.CloseCountDownInputStream@10efd7c
********************************************************************************
Exception stack is:
1. Cannot route event as component "bridge2" is stopped. Component that caused exception is: bridge2. Message payload is of type: CloseCountDownInputStream (org.mule.umo.ComponentException)
org.mule.impl.model.AbstractComponent:383 (
http://mule.mulesource.org/docs/apidocs/org/mule/umo/ComponentException.html)
********************************************************************************
Root Exception stack trace:
org.mule.umo.ComponentException: Cannot route event as component "bridge2" is stopped. Component that caused exception is: bridge2. Message payload is of type: CloseCountDownInputStream
at org.mule.impl.model.AbstractComponent.sendEvent(AbstractComponent.java:383)
at org.mule.impl.MuleSession.sendEvent(MuleSession.java:349)
at org.mule.routing.inbound.InboundRouterCollection.send(InboundRouterCollection.java:197)
at org.mule.routing.inbound.InboundRouterCollection.route(InboundRouterCollection.java:163)
at org.mule.providers.AbstractMessageReceiver$DefaultInternalMessageListener.onMessage(AbstractMessageReceiver.java:581)
at org.mule.providers.AbstractMessageReceiver.routeMessage(AbstractMessageReceiver.java:322)
at org.mule.providers.AbstractReceiverWorker$1.doInTransaction(AbstractReceiverWorker.java:107)
at org.mule.transaction.TransactionTemplate.execute(TransactionTemplate.java:40)
at org.mule.providers.AbstractReceiverWorker.doRun(AbstractReceiverWorker.java:124)
at org.mule.providers.AbstractReceiverResourceWorker.doRun(AbstractReceiverResourceWorker.java:50)
at org.mule.providers.AbstractReceiverWorker.run(AbstractReceiverWorker.java:60)
at org.mule.impl.work.WorkerContext.run(WorkerContext.java:310)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575)
at java.lang.Thread.run(Thread.java:534)
********************************************************************************
1) input file cannot be deleted on Windows because StreamMessage input stream is never closed
2) file polling overtaking itself which causes multiple stream workers to be spawned for the same file, since it could not be deleted
3) test shutting down (wrongly succeeding on Linux since it allows deletion of opened files!) and TcpWorkers swallowing InterruptedExceptions, continuing to bounce around with stopped & discarded model/component/connectors etc.
3) is what causes the insane amount of logging in mere seconds.