Hello: I am developing a process using camel routes (v. 1.4.0) inside servicemix, and, with some frequency, I found that all camel threads are waiting and my process is locked.
The process flow is, more or less: - First I have a big message, with a list of elements that must be processed. - I use a splitter to divide the message and send the parts to another endpoint (the beginning of another router). - That router makes some operations, invoking some JBI services. - Finally it creates a response-per-part and sends them to an ActiveMQ queue. I have 16 threads and, using JConsole, I see that 15 of them are locked with trace [1] and the last one has trace [2] I know the question is far more generic it should, but I am completely lost and dont know what to do. It seems that some internal queue is full, that most of my threads are sleeping while trying to insert messages in that queue and that nobody is emptying the queue. I would like to know if someone has ever seen a similar behaviour, and if there is an usual suspect to watch closely. Thank you very much in advance. dampudia ----------------------------------------------------------------------------------------------- [1] sun.misc.Unsafe.park(Native Method) java.util.concurrent.locks.LockSupport.park(LockSupport.java:118) java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await (AbstractQueuedSynchronizer.java:1841) java.util.concurrent.ArrayBlockingQueue.put(ArrayBlockingQueue.java:368) org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound (DeliveryChannelImpl.java:673) org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:172) org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:168) org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134) java.util.concurrent.ThreadPoolExecutor$Worker.runTask (ThreadPoolExecutor.java:650) java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) java.lang.Thread.run(Thread.java:595) [2] sun.misc.Unsafe.park(Native Method) java.util.concurrent.locks.LockSupport.park(LockSupport.java:118) java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt (AbstractQueuedSynchronizer.java:716) java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptib ly(AbstractQueuedSynchronizer.java:872) java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly (AbstractQueuedSynchronizer.java:1179) java.util.concurrent.CountDownLatch.await(CountDownLatch.java:199) org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:49) org.apache.camel.processor.DelegateAsyncProcessor.process (DelegateAsyncProcessor.java:66) org.apache.camel.component.direct.DirectProducer.process(DirectProducer.java:47) org.apache.camel.processor.SendProcessor.process(SendProcessor.java:61) org.apache.camel.processor.MulticastProcessor.process (MulticastProcessor.java:185) org.apache.camel.management.InstrumentationProcessor.process (InstrumentationProcessor.java:69) org.apache.camel.processor.DeadLetterChannel.process(DeadLetterChannel.java:155) org.apache.camel.processor.DeadLetterChannel.process(DeadLetterChannel.java:91) org.apache.camel.processor.Pipeline.process(Pipeline.java:101) org.apache.camel.processor.Pipeline.process(Pipeline.java:85) [...] -- View this message in context: http://www.nabble.com/Camel-threads-deadlock-tp25225906p25225906.html Sent from the Camel - Users mailing list archive at Nabble.com.
