Hello. I faced with the following issue: We have two groups of SA's . Each group contain 5 Sa's. Each SA consist of file component (poller\sender) and saxon. Poller get files from input folder pass it to saxon (via eip pipeline) and after saxon files go to out folder. Each SA group works with separate input\output folder (in1/out1 for first gpoup of SA's and in2\out2 for second group of SA's). Each SA from the group polled files with separate extention from group input folder. E.g. SA1 from group 1 polls files with *.sa1 extention from in1 folder, SA3 from group 1 polls files with *.sa3 extention from in1 folder. SA2 from group 2 polls files with *.sa2 extention from in2 folder. When I deploy all SA's from first and second groups and after that fill input (in1) folder with files- all files processed correctly without any errors. But when I deploy SA's from first group than start deploy SA's from second group and at the same time fill input folder for first, already deployed SA's group with files, than deloyment of not deployed yet SA's from second group is interapted and input files are not process by deployed SA's from first group. According to JMX console files pass through file component, seda queue for eip component is not empty, all threads for eip component freeze with the followin stack:
Name: pool-flow.seda.servicemix-eip-thread-28 State: BLOCKED on org.apache.servicemix.jbi.nmr.flow.seda.sedaf...@14f7a86 owned by: RMI TCP Connection(22)-10.98.9.169 Total blocked: 11 Total waited: 0 Stack trace: org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.createQueue(SedaFlow.java:190) org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.enqueuePacket(SedaFlow.java:180) org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doSend(SedaFlow.java:163) org.apache.servicemix.jbi.nmr.flow.AbstractFlow.send(AbstractFlow.java:123) org.apache.servicemix.jbi.nmr.DefaultBroker.sendExchangePacket(DefaultBroker.java:283) org.apache.servicemix.jbi.security.SecuredBroker.sendExchangePacket(SecuredBroker.java:88) org.apache.servicemix.jbi.container.JBIContainer.sendExchange(JBIContainer.java:894) org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.doSend(DeliveryChannelImpl.java:395) org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.send(DeliveryChannelImpl.java:431) org.apache.servicemix.common.EndpointDeliveryChannel.send(EndpointDeliveryChannel.java:88) org.apache.servicemix.common.endpoints.SimpleEndpoint.send(SimpleEndpoint.java:66) org.apache.servicemix.eip.patterns.Pipeline.processAsyncProvider(Pipeline.java:359) org.apache.servicemix.eip.patterns.Pipeline.processAsync(Pipeline.java:307) org.apache.servicemix.eip.EIPEndpoint.process(EIPEndpoint.java:165) org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:600) org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:554) org.apache.servicemix.common.AsyncBaseLifeCycle.onMessageExchange(AsyncBaseLifeCycle.java:510) org.apache.servicemix.common.SyncLifeCycleWrapper.onMessageExchange(SyncLifeCycleWrapper.java:60) org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:620) 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) What it could be? -- View this message in context: http://www.nabble.com/Servicemix-hang-up-if-process-messages-during-deployment-of-some-SA%27s-tp21035113p21035113.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
