camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ming Fang <>
Subject Re: Jms remoting failover problem
Date Mon, 23 Nov 2009 12:35:44 GMT
Thanks for looking into this problem.

According to line 76, 
        affinity = RequestorAffinity.PER_PRODUCER;
This is already the default.

The problem is this case is that the physical connection under the Producer changes if left
idle for over 30 seconds. line 105-112
        if (connection != null && connection.expiredCheck()) {
            connection = null;

        if (connection == null) {
            ActiveMQConnection delegate = createConnection(key);
            connection = createConnectionPool(delegate);

Perhaps this would be less of a problem is ActiveMQ has a way to change the idle time.
I'm going to look into Jencks to see if that can workaround this problem.
Another workaround is to set randomize=false in the ActiveMQ failover transport.

But the fundamental problem remains...
How can the Requester ensure that it is using the same physical connection as the Producer?

On Nov 23, 2009, at 6:13 AM, Claus Ibsen wrote:

> Have you tried with the option
> replyToTempDestinationAffinity=producer

View raw message