« Return to Thread: [MULE 2] Work caused exception on 'workCompleted'

RE: [MULE 2] Work caused exception on 'workCompleted'

by antoine.borg :: Rate this Message:

Reply to Author | View in Thread

Hi,
 
Can you post your configuration and the log file pls? It's hard to say what your problem is without those.
 
Cheers

A
 
Antoine Borg, Senior Consultant | Tel: +32 28 504 696 
ricston Ltd., BP 2, 1180 Uccle, Brussels, BELGIUM
email: antoine.borgantoine.borg@... | blog: blog.ricston.com | web: ricston.com 
 


From: Enrique Rodríguez [mailto:enrique.rodriguez@...]
Sent: Thursday, November 20, 2008 6:29 PM
To: user@...
Subject: [mule-user] [MULE 2] Work caused exception on 'workCompleted'

Hi, I need help from a Mule core developer to overcome this problem. I'm using Mule 2.0.2 on Linux, and after a few days it starts logging this 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. Before this scenario, I have vmQueue.dispatcher 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, o work-around it? Thanks in advance, Q.- My vmConnector config: class AbstractConnector: protected void handleWorkException(WorkEvent event, String type) { if (event == null) { return; } Throwable e = event.getException(); if (e == null) { return; } if (e.getCause() != null) { e = e.getCause(); } logger.error("Work caused exception on '" + type + "'. Work being executed was: " + event.getWork().toString()); if (e instanceof Exception) { this.handleException((Exception) e); } else { throw new MuleRuntimeException(CoreMessages.connectorCausedError(this.getName()), e); } }

View this message in context: [MULE 2] Work caused exception on 'workCompleted'
Sent from the Mule - User mailing list archive at Nabble.com.

 « Return to Thread: [MULE 2] Work caused exception on 'workCompleted'