Re: scheduler message deliver immediately

[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 disappears and ActiveMQ works
while just the web console cannot get my broker infos.(That's why I assume
that web console may take the 61616 port of broker)



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/scheduler-message-deliver-immediately-tp4718568p4718785.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

need help understanding zkSessionTimeout

[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.1.2/zookeeperStarted.html shows that
zk's "tick time" defaults to 2s.

But zk's timeout is 2 * "tick time" = 4s

Is it better to have zkSessionTimeout less than, equal to, or greater than
zk's timeout? In other words, what would be the benefits/drawbacks of
increasing zkSessionTimeout 4s, or 5s (while leaving zk's "tick time" at
2s)?

Thanks,
adam



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/need-help-understanding-zkSessionTimeout-tp4718772.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Activemq EOFException

[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
warning, and not severe afaics.



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/Activemq-EOFException-tp4681252p4718765.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: scheduler message deliver immediately

[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 Oct 31, 2016 8:02 PM, "CallMeXYZ"  wrote:

> Yes,the web console runs and show no activity. I thought it was because my
> broker takes the port of '616167' and the web console listens '61616'.
> Right?Sure that only one broker.the broker and web console cannot have the
> same port
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.
> nabble.com/scheduler-message-deliver-immediately-tp4718568p4718714.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>