Hi, I need help from a Mule core developer to overcome this problem. I'm using Mule 2.0.2 on Linux, and i am getting below error error: Work caused exception on 'workCompleted'. Work being executed was: org.mule.transport.AbstractMessageDispatcher$Worker@1abe3a
It happens on org.mule.transport.vm.VMConnector logger, and after a bit of research, I found it really happens on class
org.mule.transport.AbstractConnector, method handleWorkException(WorkEvent, String), in line 1746, in which the error is logged.
It seems that the event has an exception (event.getException != null). Oddly, the exception never gets logged, just this messge.
After this scenario is set, all VMConnectors, one by one, starts refusing requests. If I restats Mule, it works fine for a few days or so. In addition, the thread executing the method is named vmQueue.dispatcher.1502. Looks like Mule starts creating threads.
Despite the name, I'm not using queued vm connector.
I saw that others has this problem too, but didn't saw solutions. Has anyone solved it, or work-around it?
hanks in advance
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
