Hello,
after launching with xbean:activemq-stomp.xml, I can stop the server
(versions 5.3.2, 5.4.3, 5.5.1, on localhost) with activemq-admin stop
With the 5.6 snapshot, I see this error:
C:\Java\apache-activemq-5.6-SNAPSHOT\bin>call activemq-admin.bat stop
Java Runtime: Sun Microsystems Inc.
The ActiveMQ 5 Getting started guide lists Java 5 as a requirement, not 6:
http://activemq.apache.org/version-5-getting-started.html#Version5GettingStarted-PreInstallationRequirements
Is the guide out of date or has activemq-all-5.5.1.jar been compiled with
the wrong JDK?
--
View this message in
No, ActiveMQ logs on both brokers in the failover cluster seem normal, no
instance of loss of communication from each other or an unexpected reboot
of any kind.
I'm wondering if debug logging would reveal the reason for reconnections.
On Wed, Apr 11, 2012 at 4:59 AM, Torsten Mielke wrote:
> Hell
Hello,
Correct, these log lines indicate that your JBoss client has reconnected to the
broker.
As to why that happened, I don't know. However a reconnect once a day does not
sound like a bigger problem.
Is there any information in the broker log as to why the connection was shut
down?
Chee
