Re: Fail to acquire lock. Stays as "slave"

maybe try enabling trace level logging via log4j.properties and see if there is anything more in the log. You can reproduce this, right? On 4 July 2011 17:01, farhad wrote: > Hi Gary, > Yes, I know, its very odd. But both jconsole and the log say that the broker > is 'slave'!!? > Regards, Farhad

Re: Fail to acquire lock. Stays as "slave"

Hi Gary, Yes, I know, its very odd. But both jconsole and the log say that the broker is 'slave'!!? Regards, Farhad -- View this message in context: http://activemq.2283324.n4.nabble.com/Fail-to-acquire-lock-Stays-as-slave-tp3643888p3643961.html Sent from the ActiveMQ - User mailing list archive

Re: Fail to acquire lock. Stays as "slave"

That is very odd, if the lock acquire fails, the network adapters are not started, so you should not be able to connect to the broker with a jms client to send messages. On 4 July 2011 16:31, farhad wrote: > Hi, > Sorry for the previous email. Here it is in a readable format: > We've been running

Re: Fail to acquire lock. Stays as "slave"

Hi, Sorry for the previous email. Here it is in a readable format: We've been running activemq embedded brokers (5.4.2) with jboss 6.0 for a while now without any problems. We've been using four brokers in a master/slave configuration mixed with broker networks topoloy. Now we are going to run acti

Fail to acquire lock. Stays as "slave"

Hi, We've been running activemq embedded brokers (5.4.2) with jboss 6.0 for a while now without any problems. We've been using four brokers in a master/slave configuration mixed with broker networks topoloy. Now we are going to run activemq 5.5.0 as sandalone broker. In the meantime we have an odd

Monitoring ActiveMQ queue sizes via StatisticsPlugin

Hi everyone, I am quiet new to ActiveMQ and try to monitor the overall queue size. I found a nice Nagios/Icinga plugin to do so, which uses the StatisticsPlugin. Currently I am a bit puzzles, because it seems the same configuration yields different result on different host. On one host (my VM),

Re: (FIXED) STOMP transport in embedded Broker not working

Thanks for closing the loop :) On 4 Jul 2011 13:28, "SketchCND" wrote: > I added the activemq-optional artifact to my POM and this is now working. > > > org.apache.activemq > activemq-core > > > -SketchCND > > -- > View this message in context: http://activemq.2283324.n4.nabble.com/STOMP-transpo

(FIXED) STOMP transport in embedded Broker not working

I added the activemq-optional artifact to my POM and this is now working. org.apache.activemq activemq-core -SketchCND -- View this message in context: http://activemq.2283324.n4.nabble.com/STOMP-transport-in-embedded-Broker-not-working-tp3640473p3643511.html Sent from the ActiveMQ -

Re: EOFException from Stomp - heap space exhausted after enabling GC on queues

It is just a hunch based on the root cause of that issue, a removed destination reference remaining in the connection contex. Feel free to open a separate issue, to be convinced we need a test case. On 4 July 2011 11:02, James Green wrote: > How convinced are you? > > I'm minded to file this as

Re: EOFException from Stomp - heap space exhausted after enabling GC on queues

How convinced are you? I'm minded to file this as a seperate bug given the heap exceptions being thrown and the Stomp connectivity that dies completely. What is not explained in the bug report you list are the "other effects" of the bug Timothy has fixed and whether there may be any overlap in the

Re: Unacknowledged message is not redelivered

> 1. So, why should Individual acknowledgement mode be used? With individual ack mode you still need to ack *each* msg eventually. Not acking the msgs does not mean the broker will replay it. Only when acked, will the broker assume the msg got consumed and delete it on its end. There is no roll

Re: EOFException from Stomp - heap space exhausted after enabling GC on queues

this looks like a bug, but I think it may be an instance of https://issues.apache.org/jira/browse/AMQ-2524 which has just been resolved so it is available in the most current 5.6-SNAPSHOT On 4 July 2011 09:31, James Green wrote: > Getting these: > > 2011-07-03 07:41:54,330 | INFO  | Transport fai

Re: Could not correlate acknowledgment since update

I don't see any failovering happening. It just gives this warning now and then. After a while the broker stops working with an Out Of Memory error. -- View this message in context: http://activemq.2283324.n4.nabble.com/Could-not-correlate-acknowledgment-since-update-tp3622139p3643166.html Sen

EOFException from Stomp - heap space exhausted after enabling GC on queues

Getting these: 2011-07-03 07:41:54,330 | INFO | Transport failed: java.io.EOFException | org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ Transport: tcp:///127.0.0.1:53546 2011-07-03 07:49:05,893 | INFO | Transport failed: java.io.EOFException | org.apache.activemq.broker.Tran