Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (nike.apache.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
Date: Wed, 5 Feb 2014 18:07:40 -0800 (PST)
From: artnaseef <art@artnaseef.com>
To: users@activemq.apache.org
Message-ID: <1391652460821-4677512.post@n4.nabble.com>
In-Reply-To: 
 <CAKinei+Wccb1cVKQfcRedQA_jTjredZsA2LsMVm0MftppGBvDA@mail.gmail.com>
References: 
 <CAKinei+Wccb1cVKQfcRedQA_jTjredZsA2LsMVm0MftppGBvDA@mail.gmail.com>
Subject: Re: Broker Hangs after some time - or does nothing.
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

There are many things to check.

First off, I have a little confusion.  You metion no log messages on the
client or server and then show log messages.  By server, do you mean the
broker or something else?

Troubleshooting steps:
* When flow stops, check the broker for active client connections via the
webconsole or JMX.
* Check consumer and producer counts for the destinations.
* If the failover transport is being used, be sure to use a
ConnectionListener and TransportListener to receive notifications of lost
connection to the broker.  Note that you should get a log message if the
failover transport loses connection, so this may not be necessary.
* Check broker JVM memory (especially Heap and PermGen)

Also, if the broker is running out of memory due to having too many messages
(i.e. slow consumer problem), that could cause the broker to stop
functioning.


--
View this message in context: http://activemq.2283324.n4.nabble.com/Broker-Hangs-after-some-time-or-does-nothing-tp4677506p4677512.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.