Re: Network of Brokers: XAException on Failover

Maybe I'm not using the network of brokers in the correct manner. Should a network of brokers be used for HA, or just scalability and load balancing? We are not concerned with the loss of a few messages if one broker fails; however, we want to make sure there is not a single point of failure in

Re: Network of Brokers: XAException on Failover

I did mean 5.12. -- View this message in context: http://activemq.2283324.n4.nabble.com/Network-of-Brokers-XAException-on-Failover-tp4702355p4702359.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Network of Brokers: XAException on Failover

Jboss 6.1 EAP ActiveMQ 5.1.2 I'm trying to connect Jboss to an ActiveMQ high availability cluster. When I kill one ActiveMQ server and Jboss fails over to the backup server everything works as expected (messages are still passed), but I see the following error message every two minutes: [com.arj

Re: Garbage collecter out of memory

Thanks for your help Tim. It was the application heap size. I upped it to 2G and the errors disappeared. I think I didn't see the errors with HornetQ because I tested on a day whey we had very little data to process. I feel like an idiot for taking two days to figure it out, but I did learn a lo

Re: Garbage collecter out of memory

FYI the image from the previous post was for the ActiveMQ process. This is the application process: -- View this message in context: http://activemq.2283324.n4.nabble.com/Garbage-collecter-out-of-memory-tp4702160p4702192.html

Re: Garbage collecter out of memory

Hi Tim, Thanks for the reply. If I force a full GC, memory usage does not drop. I'm not actually not using all of my memory. Execution is slowing down to the point that messages are timing out (presumably due to excessive GC). I increased the size of my JVM and the change had no effect. For s

Garbage collecter out of memory

Hi, I have a webapp running on Jboss that is currently using HornetQ for messaging. I'm attempting to switch to ActiveMQ but running into some annoying issues. Everything starts with no issue and messages are transfered as expected, but after running for a short period of time, I start getting t