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: domain of bruce.snyder@gmail.com
 designates 209.85.218.159 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=gX7ffUKt2mPeliOD50TjndUZ1dFb5GHvVXhKb4XOSoNrDOf0IZFZc7z3QVQzOZdXOI
         M0tFDpBDsvswOAdVU+tiIf7fKQw6cin/VFODk1X1WVCUDLuoT7cSlH1ao1mnS6/FcQbG
         kjD7DZL9vMu0QbquX/7yy7oa2PX5yZhFXF76I=
MIME-Version: 1.0
In-Reply-To: <270344.70776.qm@web59503.mail.ac4.yahoo.com>
References: <270344.70776.qm@web59503.mail.ac4.yahoo.com>
Date: Mon, 23 Mar 2009 14:23:52 -0600
Message-ID: <7b3355cb0903231323l405a3d3flad1e39f4d7647adb@mail.gmail.com>
Subject: Re: ActiveMQ 5.2 - broker stops sending messages
From: Bruce Snyder <bruce.snyder@gmail.com>
To: users@activemq.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Mon, Mar 23, 2009 at 1:53 PM, Ron Reynolds <tequilaron@ymail.com> wrote:
> i know it's a vague subject line and i'm almost certain it's been asked b=
efore but i'm under a tight deadline on a near-production system and i need=
 help. =A0the situation is this:
>
> - single broker (5.2) with only 4 queues (not topics)
> - default broker config with prefetchPolicy.queuePrefetch=3D0 added to br=
oker's connection pool brokerURL attribute
> - single client using failover URL (in anticipation of a second broker on=
ce the system is stable)
> - client using Spring-JMS.
> - client-ack, small messages, 7-second retry on the client, using PooledC=
onnectionFactory wrapped around ActiveMQConnectionFactory
> - no transaction management added.
> - both client and server are Linux (CentOS 5.x i think) w/ Sun JVM 1.5.0_=
11.
>
> the situation is that the system, after running well for an hour or more =
(typically not more than 24) it will suddenly stop sending notification to =
the client of new messages in one of the queues (need for it to repro to te=
st if it happens for other queues). =A0a QueueBrowser shows the messages ju=
st fine, but a receiveMessages() with null selection criteria times out bef=
ore any messages are returned. =A0i'm able to insert new messages into the =
queue but the client still gets no notification.
>
> another developer is currently looking at OpenMQ or other JMS implementat=
ions to avoid this issue but it has to be a config issue, yes?

In the conf/activemq.xml file, what is the memoryUsage limit set at
currently? If it's still at the default of 20mb, I suggest raising it
to a more appropriate limit. This is the memory limit for the entire
broker and should be big enough to hold all messages in memory at any
given point in time. Remember that this needs to remain in accordance
with the JVM memory settings ( the java -Xmx setting).

Also, when the broker is not dispatching messages to clients, grab a
thread dump to see where exactly it's hanging. A thread dump can be
triggered using a kill -QUIT <pid> on Unix or a ctrl-break on Windows
or the jstack utility.

There's also an open issue for something similar to this in AMQ-2009:

http://issues.apache.org/activemq/browse/AMQ-2009

Even so, I still highly suggest getting a thread dump to see where
it's hanging.

Bruce
--=20
perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=3D6-E+G-N>61E<D\!G;6%I=
;\"YC;VT*"
);'

Apache ActiveMQ - http://activemq.apache.org/
Apache Camel - http://camel.apache.org/
Apache ServiceMix - http://servicemix.apache.org/

Blog: http://bruceblog.org/