Re: network of brokers reduced capacity

It seems that working in debug mode is much more heavy for broker to broker message, then for broker to consumer message, which cut the capacity of the server (#tx/sec) in half. once I set debug off, there was no diffrence for broker-broker, and broker-consumer -- View this message in context:

network of broker - update and rebalance not working

Hi I'm having trouble making the *updateClusterClients=true rebalanceClusterClients=true* work I have a network of brokers size 2 with the following brokers configuration *beans xmlns=http://www.springframework.org/schema/beans; xmlns:amq=http://activemq.apache.org/schema/core;

Re: ActiveMQ Master/slave with MySQLCluster backend

This need some work. On 5.6, a single broker can deal with a failover of the jdbc store. The difficulty is locking in the master/slave case, or peer cluster case. The current lock impl (who's job it is to get an exclusive lock on the store) treats failure of a lock as a fatal event and stops the

Reply:Re: ActiveMQ Master/slave with MySQLCluster backend

I had set up two brokers based on master-slave mode. What I'm suffering are the two problems: 1, NDB store engine of Mysql cluster does not support distributed lock so brokers based on master-slave mode fails to get the exclusive lock and finally two masters are bringing up. 2, With the store

Reply:network of broker - update and rebalance not working

Seems the same trouble I got into some days ago. What I want brokers to do is to update clients with urls of brokers of joining or leaving the cluster, and rebalance clients for us too. I set up two networked brokers and follow a instruction in a blog(cannot remember the url) with setting three

Re: Transaction not started XA problems

Just an FYI to my question below. I went back and examined my camel endpoint configuration for JMS versus my raw DMLC configuration for non camel JMS endpoints. The one major difference was the cache setting. When I added this to the jmsconfig, the OOM problems on the activemq broker went away:

Re: Apollo and websockets

Apollo does not yet support WebSockets. :( Issue https://issues.apache.org/jira/browse/APLO-145 has already been raised. And I totally agree with it. We should suport it. -- View this message in context: http://activemq.2283324.n4.nabble.com/Apollo-and-websockets-tp4200336p4345411.html Sent

JDBC based Master/slave configuration

As it was mentioned in http://activemq.2283324.n4.nabble.com/activemq-user-Network-of-brokers-and-db-schema-td2342357.html#a2342360 Its technically possible to patch the JDBC message store to include a broker ID column in all the tables to allow the same JDBC database to be used for multiple

Re: Confusing docs about disabling flow control

So is the community abandoning its documentation in favor of the fuse documentation? I've seen similar replies a few times to go look at fuse docs vs. what is on the activemq.apache.org site before. Would be nice to have a single concise location to find the most

Re: Apollo and websockets

Since it's been requested so much I started working on it today and made good progress. The next snapshot build of apollo 1.1-SNAPSHOT should have WebSocket support. Just add connectors for the 'ws://' or 'wss://' protocols to the apollo.xml file. For example: connector id=ws