activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dege <deg...@pointclickcare.com>
Subject Re: Failover not working with distributed queue
Date Fri, 09 Feb 2007 22:21:06 GMT

Just as a follow up, setting the failover to false results in an out of
memory error quite quickly if where you are bridging to is not up.
in the log i see

09/02/2007 17:16:58.880 [Thread-23] INFO  Establishing network connection
between from vm://pccapp?network=true to tcp://localhost:62001

09/02/2007 17:16:59.868 [Thread-23] WARN  Could not start network bridge
between: vm://pccapp?network=true and: tcp://localhost:62001
over and over again when the target is not up, each time with a different
thread id.
Memory consumption continues to climb and climb until it eventually throws
an out of memory error.  This is without any other activity in the app.  
Resetting failover to true fixes the issue but then we're back to the local
and remote brokers not synching up if the remote broker goes down for a
period.
-- 
View this message in context: http://www.nabble.com/Failover-not-working-with-distributed-queue-tf3176112s2354.html#a8894638
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Mime
View raw message