activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dbrondy <dbro...@yahoo.fr>
Subject Re: Problem while upgrading from ACTIVEMQ 5.2 to 5.3.2
Date Wed, 21 Jul 2010 07:30:44 GMT

Hi Gary,

I run this example on a unique computer using the IP adress, and I couldn't
reach it to work fine. It seems working fine when you are running this
configuration using the real computer and the hostname in the Transport and
Network connector url.

Moreover, the most important things is that I'm suspecting a strong thread /
memory leakage in this ActiveMQ version (probably present since 5.3 before I
don't have such behavior in 5.2) when the other ActiveMQ nodes are not
present.

Following is two Jconsole screenshots of one broker instance. I was running
this configuration : 4 broker in Nob using static connector and 2 element
are dead.

http://old.nabble.com/file/p29222688/sc1.jpg 
http://old.nabble.com/file/p29222688/sc2.jpg 

I think I'm gona submit this to the ActiveMQ bug tracker.

denis


Gary Tully wrote:
> 
> quick thought, do your transport connectors use tcp://localhost ?
> if so, you need to use a wildcard address tcp://0.0.0.0 to listen on
> all available interfaces, not just the loopback address:
> see: https://issues.apache.org/activemq/browse/AMQ-2094
> 
> On 20 July 2010 09:55, dbrondy <dbrondy@yahoo.fr> wrote:
>>
>> Hi everyone,
>>
>> As we didn't find any solution to our problem described here :
>> -
>> http://old.nabble.com/Strange-behavior-using-failover-and-network-of-broker-td29107245.html
>>
>> we tried to upgrade from ACTIVEMQ 5.2 to 5.3.2.
>>
>> It seems the same configuration does not work at all... To summarize what
>> is
>> completely describes in the previous post, we have 4 BROKER all connected
>> together. Now, on ACTIVEMQ 5.3.2, if a producer sends message though
>> BROKER1, the receiver needs to be connected on that broker to receive the
>> message.
>> I tried a lot of configuration changes by playing with TTL, Duplex,
>> DynamicOnly, using multicast discovery protocol and I can't let it work.
>>
>> Please help... I'm disappointed.
>>
>> denis
>>
>>
>> --
>> View this message in context:
>> http://old.nabble.com/Problem-while-upgrading-from-ACTIVEMQ-5.2-to-5.3.2-tp29212739p29212739.html
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
>>
> 
> 
> 
> -- 
> http://blog.garytully.com
> 
> Open Source Integration
> http://fusesource.com
> 
> 

-- 
View this message in context: http://old.nabble.com/Problem-while-upgrading-from-ACTIVEMQ-5.2-to-5.3.2-tp29212739p29222688.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Mime
View raw message