Hello. I'm struggling with this issue too. I want to clarify this issue.
According to JMX console the threads are waiting for something to happen. So, if we have a lot of components, i.e 10, then for each component thread is allocated and during processing of message Servicemix uses at least 10 threads. If I configure to use 100 threads in servicemix in serviceix.properties then Servicemix creates 100 threads with the component A and 10-1 threads for each of other components. I have suggestion, that SMX incorrectly manages thread pool for processing. Also, if we send small amount of messages, then all of the messages are processed correctly and JConsole shows all threads are in WAITING mode and all ActiveMQ queues are empty. When we send a lot of messages, then SMX hangs and no further processing occures and JConsole shows, that there are several free threads with component A and threads which running components B, C and MessageRouter are in TIMED_WAITING mode. On Thursday 18 September 2008 17:26:46 splatch wrote: > For endpoint you can configure connection factory using spring beans: > <jms:consumer service="...." endpoint="endpoint" > .... > connectionFactory="#connectionFactory" > /> > > <bean id="connectionFactory" > class="org.apache.activemq.ActiveMQConnectionFactory"> > <property name="brokerURL" > value="tcp://locahost:61616?jms.useAsyncSend=true" /> > </bean> > > But I really don't know how to configure ServiceMix instance to use this. > > Regards, > Luke > > pvn wrote: > > Hi > > > > How can I configure servicemix to use activemq in the async mode? > > > > from here this is not clear > > http://activemq.apache.org/async-sends.html > > > > thanks, > > Vladimir. -- Best Regards, Oleg Atamanenko. -- Fortune of the day: "It takes all sorts of in & out-door schooling to get adapted to my kind of fooling" -- R. Frost
signature.asc
Description: This is a digitally signed message part.
