Faster detection of failure on network connections in "cable pull" scenario

We are doing "break testing" on our clustered deployment and are running into an issue with activemq being slow to notice a node that has been "cable pulled". We are seeking advice on how to best configure the connections between the brokers to notice this error quickly. We have a producer box

Re: High CPU load with network connector, failover transport

Created https://issues.apache.org/jira/browse/AMQ-5605 -- View this message in context: http://activemq.2283324.n4.nabble.com/High-CPU-load-with-network-connector-failover-transport-tp4691798p4691829.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

[ANNOUNCE] ActiveMQ-CPP Version 3.8.4 Released

Hi Everyone, Its official, AcitveMQ-CPP v3.8.3 has now been released. This release contains a fixes for some issues found since the 3.8.3 release that improve overall client stability. The Wiki page for the release is here: The l

Re: "java.lang.OutOfMemoryError" in consumer application

Hi, It checked it and it was because of the client application was running more processes then the ulimit configured. Thanks, Anuj -- View this message in context: http://activemq.2283324.n4.nabble.com/java-lang-OutOfMemoryError-in-consumer-application-tp4691751p4691810.html Sent from the Act

Re: High CPU load with network connector, failover transport

Pleas submit a bug in JIRA for it, ideally with a unit test that shows the problem (though I'm not quite sure how you'd write a unit test to confirm that a particular thread isn't spinning a core so that might be wishful thinking). On Feb 20, 2015 6:59 AM, "Tim Robbins" wrote: > By the way, I've

Re: "java.lang.OutOfMemoryError" in consumer application

Keep in mind too that the native thread limit is for the user, counting all processes running as that user on the box, so if you're doing other things on that box as that user you can contribute to this problem. A co-worker ran one of our brokers out of threads after accidentally firing up a coupl

Re: High CPU load with network connector, failover transport

By the way, I've noticed Lars has run into the same issue and posted via Nabble but it hasn't turned up on the mailing list yet: http://activemq.2283324.n4.nabble.com/Using-a-NetworkConnector-results-in-high-CPU-load-td4691627.html > On 20 Feb 2015, at 12:16 pm, Tim Robbins wrote: > > Hi, >

Re: ActiveMQ broker is stopping after it is unable to destroy inactive durable subscriber.

Hi We are facing this problem again. In our setup we run activemq primary and failover broker, previously this issue happened with primary broker and failover took over properly. Today this same issue happen again with failover broker. Can somebody help here on why is this happening. -- View