Thanks for the input and suggestions. As of now, I have removed the EIP component from the flow as I had observed the exchange waiting for threads to finish.
Also, I have defined separate connection pool for the jms components as suggested in a different thread. I am seeing much better performance, but will need to monitor for a few days to. Eighty8 wrote: > > I found I had to throttle my messages by sleeping ~250-500ms apart. I > recommend buying a YourKit license and attaching it to your server. > You'll see a lot more of what's going on under the hood. Look for 'lots > of read' in the threads indicating blocks that are waiting to clear. > > I have not had success, yet, using component.properties to controls the > eip and saxon LifeCycles, but am continuing to try to get that working. > > You can inspect the configurable properties by enabling jetty on your ESB > and access jmx-console. > Good luck. > > > subh wrote: >> >> I have a simple flow as below >> >> External message producer --> SMX JMS queue --> SMX Bean --> Camel router >> --> SMX JMS Topic >> >> The servicemix bean has the business logic to generate the outgoing >> message. >> To forward the message onto the next service, I am using >> ServiceMixClient. >> >> I am using the ClientFactory to create a instance of the client. >> >> ClientFactory factory = new >> InitialContext().lookup(ClientFactory.DEFAULT_JNDI_NAME); >> ServiceMixClient client = factory.createClient(); >> >> But after processing 1000 - 1500 messages, the Servicemix bean component >> becomes very slow to respond. On checking the log, I see that the bean >> thread count increases considerably and the expired threads are not >> garbage collected. >> >> Due to this, all incoming messages are getting blocked which forces us to >> restart the servicemix server. Once it is restarted, the processing >> becomes very fast and we come to the same situation again in a day or so. >> >> Am I doing something wrong by using the ServicemixClient inside the bean? >> If no, then what are the best practices for using the Servicemix client >> class. >> >> Are there alternative ways to specify the "target service" from the SMX >> bean endpoint? >> >> Any hint or suggestion would be helpful. >> >> I am using activemq5.3 and servicemix 3.3 >> >> Regards >> Subh >> > > -- View this message in context: http://old.nabble.com/ServicemixBean-thread-issue..-tp27714350p27772707.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
