not sure if this is helpful but you can switch the container
implementation on the component
<bean id="jms" class="org.apache.camel.component.jms.JmsComponent">
<property name="consumerType" value="ServerSessionPool"/>
<!-- other properties here -->
</bean>
look at the ConsumerType enum for more choices
On 11/8/07, gent911 <[EMAIL PROTECTED]> wrote:
>
> Howdy,
>
> Set-up
> -------
> Spring 2.1
> Camel 1.2
> ActiveMQ 5 the latest snapshot
>
> Problem
> ---------
> DefaultMessageListenerContainer is restarted all the time in a new thread.
>
> Such a behaviour is not exactly what I want to see, I'd like to use pooling
> and finally stop the thread from constant restarting.
> I have written a small example, but I cant seem to find the appropriate
> solution, looking through the mailing list did not bring any results either.
>
> Here is a the snippet from spring configuration:
>
> --- cut ---
> <bean id="jmsFactory"
> class="org.apache.activemq.pool.PooledConnectionFactory">
> <property name="connectionFactory">
> <bean class="org.apache.activemq.ActiveMQConnectionFactory">
> <property name="brokerURL" value="tcp://localhost:6666" />
> </bean>
> </property>
> </bean>
>
> <bean id="jms" class="org.apache.camel.component.jms.JmsComponent">
> <property name="connectionFactory" ref="jmsFactory" />
> <property name="camelContext" ref="camel" />
> </bean>
>
> <bean id="queueTest" factory-bean="camelEndpointFactory"
> factory-method="getEndpoint">
> <constructor-arg value="jms:queueTest" />
> </bean>
> </code>
> --- end ---
>
> It seems to work alright with Spring's
> ServerSessionMessageListenerContainer, but refuses to function with Camel.
> I'd appreciate any hint, thnx.
>
> --
> Regards
> --
> View this message in context:
> http://www.nabble.com/DefaultMessageListenerContainer%2C-pooling-problem-tf4772431s22882.html#a13651972
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>
