You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by pratibhaG <pr...@in2m.com> on 2008/08/27 07:22:29 UTC

Too many threads created if jms consumer su is deployed in hotdeploy

I have a operation which uses jms consumer SU. It listens to a queue.
Here is the configuration:

<beans xmlns:jms="http://servicemix.apache.org/jms/1.0"
       xmlns:err="http://servicemix.in2m.com/operations/errorhandler"
       xmlns:amq="http://activemq.org/config/1.0">
	<jms:consumer service="err:ResolvedErrorConsumerService"
                  endpoint="resolvedErrorConsumerEndpoint"
		          targetService="err:ResolvedErrorConsumerService"
                  destinationName="resolved.error.queue"
                  connectionFactory="#connectionFactory"
				  marshaler="#jmsConsumerMarshaler"/>
		
	<bean id="jmsConsumerMarshaler"
class="com.in2m.servicemix.common.marshaller.jms.DefaultJmsConsumerMarshaler"/>
    <amq:connectionFactory id="connectionFactory"
brokerURL="tcp://localhost:61616" />

</beans>

When I put this in smx/hotdeploy total started threads goes on increasing
and never comes down. This happens only when I use new endpoint for jms that
is jms:consumer.
If I use jms:endpoint it does not happen. Also If I have jms:consumer which
listens to topic with other configuration same as above, it does not happen.

Why the behavior is so? How can I avoid it? Or am I missing something? 

Here are the images showing it.

http://www.nabble.com/file/p19174829/AfterKeepingOpeartionContainingJmsConsumer1.jpg
AfterKeepingOpeartionContainingJmsConsumer1.jpg 
http://www.nabble.com/file/p19174829/beforeKeepingOpeartionContainingJmsConsumer1.jpg
beforeKeepingOpeartionContainingJmsConsumer1.jpg 


-- 
View this message in context: http://www.nabble.com/Too-many-threads-created-if-jms-consumer-su-is-deployed-in-hotdeploy-tp19174829p19174829.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.