The maxThreadsActive of vm receiver-threading-profile is 119, but it
looks like the threads are exhausted.
I don't know what can cause that, does anybody has some experience
with dealing this?
Any help will be appreciated.
[1/14/09 8:46:09:716 GMT+08:00] 00000063 SystemOut O 08:46:09,0460
ERROR [asyncVm.receiver.68] DefaultExceptionStrategy.l
ogException(376) | Caught exception in Exception Strategy: null
edu.emory.mathcs.backport.java.util.concurrent.RejectedExecutionException
at org.mule.util.concurrent.WaitPolicy.rejectedExecution(WaitPolicy.java:56)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:765)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1288)
at org.mule.work.ScheduleWorkExecutor.doExecute(ScheduleWorkExecutor.java:41)
at org.mule.work.MuleWorkManager.executeWork(MuleWorkManager.java:269)
at org.mule.work.MuleWorkManager.scheduleWork(MuleWorkManager.java:215)
at org.mule.transport.TransactedPollingMessageReceiver.poll(TransactedPollingMessageReceiver.java:144)
at org.mule.transport.PollingReceiverWorker.run(PollingReceiverWorker.java:47)
at org.mule.transport.vm.VMMessageReceiver$VMReceiverWorker.run(VMMessageReceiver.java:192)
at org.mule.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:810)
--
My Blog:
http://leegorous.net/blog
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
Can you post your configuration too, please?
A
Antoine Borg, Senior Consultant | Tel: +32 28 504 696
ricston Ltd., BP 2, 1180 Uccle, Brussels, BELGIUM
email: antoin...@ricston.com | blog: blog.ricston.com | web: ricston.com