Re: scheduler message deliver immediately

2016-11-01 Thread Tim Bain
The web console is typically configured to use port 8161 (see http://activemq.apache.org/web-console.html) unless you've changed it. Are you saying you access the web console on 61616? When you shut down your broker, can you access the web console? You may want to post your configuration. On Oc

Re: Activemq EOFException

2016-11-01 Thread mlange
In fact, this always happens when a connection stops... If you have a network of brokers and you stop one, you'll see this exception in the other brokers. If your client stops, same... Maybe this exception deserves to be handled like "Connection has disconnected." but apart from that... it's a war

need help understanding zkSessionTimeout

2016-11-01 Thread Adam Whitney
I'm using activemq 5.13.3 with replicatedLevelDB and I'm wondering how to best configure the zkSessionTimeout setting as it relates to ZooKeeper's "tick time". http://activemq.apache.org/replicated-leveldb-store.html shows that zkSessionTimeout defaults to 2s. https://zookeeper.apache.org/doc/r3.

Re: scheduler message deliver immediately

2016-11-01 Thread CallMeXYZ
I do understand the web console take the localhost:8161.But I always get 'java.net.BindException: Address already in use: JVM_Bind exception. ' if my broker url is 61616. Either I change my broker url to 61617 or change the activemq.xml configuration // to /tcp://0.0.0.0:61616/,then the exception