See http://servicemix.goopen.org/site/why-does-servicemix-seems-to-hang-after-some-processing.html
This is usually because one of the component do not send the DONE status or does not reply to an InOut mep. Cheers, Guillaume Nodet On 6/14/06, Andreas Held <[EMAIL PROTECTED]> wrote:
Hi I am trying to integrate ServiceMix in JBoss and generally things are working out. However, I now came across the following problem: I have two Pojos, a sender, implementing ComponentLifecycle, and a receiver, implementing ComponentLifecycle and MessageExchangeListener. I am using the following servicemix.xml: <beans xmlns:sm="http://servicemix.apache.org/config/1.0"; xmlns:foo="http://servicemix.apache.org/cheese/"; xmlns:jsr181="http://servicemix.apache.org/jsr181/1.0";> <sm:container id="jbi" useMBeanServer="false" createMBeanServer="false" dumpStats="true" statsInterval="10"> <sm:activationSpecs> <sm:activationSpec componentName="msgSender" service="foo:msgSender" destinationService="foo:msgReceiver"> <sm:component><bean xmlns="http://xbean.org/schemas/spring/1.0"; class="ch.bbp.igt.comm.ServiceMix.PojoSender" /></sm:component> </sm:activationSpec> <!-- direct destination, no routing --> <sm:activationSpec id="msgReceiver" service="foo:msgReceiver"> <sm:component><bean xmlns="http://xbean.org/schemas/spring/1.0"; class="ch.bbp.igt.comm.ServiceMix.PojoReceiver "/></sm:component> </sm:activationSpec> </sm:activationSpecs> </sm:container> </beans> Everything works fine so far. However, if I start a loop, simply pushing messages, then I noticed that after about 1050 messages nothing goes anymore. This means, messages are being sent but not received anymore. The magical number is usually between 1053 and 1055 messages. Anybody has an idea as to what is going on? Regards Andreas
