On 02/09/2016 06:11 AM, Januszek wrote:
> I am using following broker URL:
> failover(tcp://broker1,tcp://broker2)randomize=false&jms.useAsyncSend=false&jms.dispatchAsync=false&maxReconnectAttempts=30&maxReconnectDelay=3000
>
> The problem is that upon a failover, all producers are closed, but once the
> connection is reatempted to the second broker, the same pooled CLOSED
> producers are picked by getMessageProducer:
>
> @Override
> public MessageProducer createProducer(Destination destination) throws
> JMSException {
> return new PooledProducer(getMessageProducer(destination),
> destination);
> }
>
> Is this a bug?
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/ActiveMQ-how-to-deal-with-producer-is-closed-tp4707279p4707283.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
When do the producers close, after the maxReconnectAttempts is hit and
the reconnection logic stops trying or immediately? You might consider
trying to boil this down to a unit test similar to others in the
activemq-pool project to try and show the problem in the simplest form.
--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/
