This content has been marked as final.
Show 2 replies
-
1. Re: SMX4 JMS Durable Subscriber and OSGi LifeCycle
davestanley Jun 22, 2009 11:51 AM (in response to fouquet.f)Hi
Can you paste your connection factory configuration. Its just a guess but I'm wondering if perhaps you are using a pooled connection factory and when you do the refresh the destroy-method is not being called on the connection.
<bean id="pooledFactory" class="org.apache.activemq.pool.PooledConnectionFactory" destroy-method="stop"> .... </bean>
(It could also be a bug of course..)
Regards
/Dave
-
2. Re: SMX4 JMS Durable Subscriber and OSGi LifeCycle
fouquet.f Jun 22, 2009 5:16 PM (in response to davestanley)Hi ,
I think your idea is perhaps the solution , actually i'm using the connection factory by default because the transaction manager is activated.
So I'm calling the Connection factory behind OSGI refrence like that :
<osgi:reference id=connectionFactory interface=javax.jms.ConnectionFactory />
Have you a better solution ? Does I need to declare a method to propertly close the connection on refresh ?
Regards