activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Strachan" <>
Subject Re: Timeout and Failover on a queue
Date Tue, 27 Nov 2007 12:15:12 GMT
On 27/11/2007, Jason Rosenberg <> wrote:
> James,
> In this case, I am creating a connection for the purspose of sending a
> message (so not a message listener).  I am using the Spring JmsOperations
> template, and just injecting the connectionFactory property  for the
> jmsOperations object on initialization.
> The connectionFactory is org.jencks.amqpool.PooledConnectionFactory.  I
> presume it's up to the factory code to properly dispose of the failed
> connection's resources.  I also had the same result configuring it with the
> ActiveMQ factory, org.apache.activemq.pool.PooledConnectionFactory.
> In each case the pooled connection factories in turn use a
> 'connectionFactory' object of
> org.apache.activemq.ActiveMQConnectionFactory....
> What I've noticed is that this configuration works fine, if I use a simple
> TcpTransport.  That is, if the connection fails, the connection factory
> seems to dispose of the resources and create a fresh one for the next
> attempt, and so it recovers quickly when the broker recovers.
> Somehow, the FailoverTransport must fail in a different way, since the
> connection factory doesn't detect that it needs to remove it and create a
> new object on the next request.
> Finally, I've also seen that the FailoverTransport, if configured without
> maxReconnectAttempts, doesn't shutdown cleanly, if there's no broker
> present.  It hangs, or throws an exception.   I provide the
> destroy-method="stop" on the pooled connection factory object.
> Thanks for any help,

Do you have a test case that demonstrates your issue?


Open Source Integration

View raw message