ActiveMQ CPP 3.9.3 PriorityBackup not working

The priroity backup feature isn't working for me and am having the same issue as explained by another user on StackOverflow http://stackoverflow.com/questions/27114156/issues-with-activemq-3-8-3-cpp-prioritybackup-not-working I'm still facing the same issue with version 3.9.3. Is it an open issue/

Re: Producer count keeps increasing

We'v found the leaking client by checking the producer count of the queues one by one in JConsole. -- View this message in context: http://activemq.2283324.n4.nabble.com/Producer-count-keeps-increasing-tp4714087p4714138.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Queue size from client side

Have you looked at the Statistics Plugin? http://activemq.apache.org/statisticsplugin.html > On Jul 19, 2016, at 5:51 AM, khandelwalanuj > wrote: > > Hi, > > How to check Queue size from ActiveMQ java client ? > > Thanks, > Anuj > > > >

Large amount of PageOverflowIOExceptions per second

I see a large amount of PageOverflowIOExceptions being thrown (~ 60/sec) when producing messages. Is this to be expected or does this perhaps indicate an issue in the broker configuration? (note the exception doesn't bubble up, it is caught internally to handle a "split" situation.)

Re: To be IOT mqtt middleware server

ok，i will try this feature before i change into other middleware，because i have experience of activemq clusting，i don't want to give up so quickly. thx. -- View this message in context: http://activemq.2283324.n4.nabble.com/To-be-IOT-mqtt-middleware-server-tp4714037p4714072.html Sent from the

Re: Producer count keeps increasing

Yes, we have many clients produces messages and it's possible that some of the clients didn't close the producer properly. We will check them closely. Meantime, is there any way to prevent this at the server side? For example, if the client network connection is broken, will the orphan producer get

Queue size from client side

Hi, How to check Queue size from ActiveMQ java client ? Thanks, Anuj -- View this message in context: http://activemq.2283324.n4.nabble.com/Queue-size-from-client-side-tp4714102.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Master broker not restarting cleanly after errors - Address already in use

Update - it seems this is fixed if I updated my activemq.xml config to include: http://www.springframework.org/schema/beans"; class="org.apache.activemq.hooks.SpringContextHook" /> I'm not sure why the Puppet ActiveMQ module doesn't set this. Now, I just have to work out why

Master broker not restarting cleanly after errors - Address already in use

Hi folks - I'm testing a system using ActiveMQ 5.9.1 with an NFS server for shared filesystem master/slave I'm trying to set up and test failover and fail-back. I'm using Jepsen to fake a network split, where the Master broker can't communicate with the NFS server - after some headaches I have it

Re: Producer count keeps increasing

In your client code, it sounds like you're calling session.createProducer() many times, possibly in a loop. Are you closing each producer when you're done with it, before you create the next one? If not, the resource leak is in your code, not ActiveMQ's. Tim On Jul 19, 2016 5:41 AM, "RuralHunte

Producer count keeps increasing

Hi, I'm using activemq 5.13.3. I'm seeing the producer count on the broker side keeps increasing and never shrinks. I inspected the value TotalProducerCount of the broker via jmx. And it is also verified by the class count of org.apache.activemq.broker.jmx.ProducerView in jvm heap class histogram.

Re: Consumer does not reconnect

Can you share your code in form of a small example? It depends a bit how you do the consumer. In case you use an event based consumer you might need to set an exception listener. http://docs.oracle.com/javaee/6/api/javax/jms/Connection.html#setExceptionListener(javax.jms.ExceptionListener) You

Re: Consumer does not reconnect

Hi Christian, thanks for the answer. We tried that already with different values from 1 sec to 30 sec. Did not work out. Also leaving the PooledConnectionFactory out did not help. And all of this only occurs in the consumer case. The producer pics up the failover nicely. Anything else that might