Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of torsten@fusesource.com
 designates 74.125.245.84 as permitted sender)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: MessageListener not delivering any more messages at some point
From: Torsten Mielke <torsten@fusesource.com>
In-Reply-To: <20120530114448.DAEF.60BA733C@jeremias-maerki.ch>
Date: Wed, 30 May 2012 11:49:31 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <F36E59A2-686D-4733-9FF4-FCA7043BF73D@fusesource.com>
References: <20120530112530.DAEB.60BA733C@jeremias-maerki.ch>
 <738677FE-83DA-4E5F-B0C0-A75A7766047C@fusesource.com>
 <20120530114448.DAEF.60BA733C@jeremias-maerki.ch>
To: users@activemq.apache.org

Hhm, SMX 4.4.1 deploys ActiveMQ 5.5.1 just nicely into its OSGi =
container.=20

On May 30, 2012, at 11:44 AM, Jeremias Maerki wrote:

> Hi Torsten,
>=20
> thanks. Yes, I've made experiments with 5.5.1 on the server side but =
had
> trouble getting it up reliably in my OSGi environment so I'm hesitant =
to
> upgrade on the server side. However, the problem resides mainly in the
> client AFAICS, and that one uses 5.5.1 already. I guess I'll take a =
peek
> at 5.6.0 to see if it looks better there.
>=20
>=20
> Jeremias Maerki
>=20
>=20
> On 30.05.2012 11:30:04 Torsten Mielke wrote:
>> Hello,
>>=20
>> ActiveMQ 5.3.0 is really old. Have you thought of upgrading to the =
latest broker release 5.5.1?
>> Chances aren't too bad that your problem has been resolved.=20
>>=20
>>=20
>>=20
>> Torsten Mielke
>> torsten@fusesource.com
>> tmielke@blogspot.com
>>=20
>>=20
>> On May 30, 2012, at 11:25 AM, Jeremias Maerki wrote:
>>=20
>>> No ideas? As a work-around I'm now thinking about running a =
scheduled
>>> task that restarts the MessageListener every hour. That's a =
work-around
>>> that shouldn't really be necessary, right? A colleague told me =
yesterday
>>> that he did exactly that in a personal project of his. So, I'm =
probably
>>> not the only one with this problem, although I couldn't find =
anything
>>> related to that on the net.
>>>=20
>>> Thanks,
>>> Jeremias Maerki
>>>=20
>>>=20
>>> On 25.05.2012 12:23:54 Jeremias Maerki wrote:
>>>> Hi,
>>>>=20
>>>> I've got an ActiveMQ 5.3.0 broker running in one JVM.
>>>>=20
>>>>       <transportConnectors>
>>>>           <transportConnector name=3D"openwire" =
uri=3D"tcp://localhost:19616"/>
>>>>       </transportConnectors>
>>>>=20
>>>> Another application (different JVM but currently on the same =
machine)
>>>> connects to that broker to receive messages from a single queue =
through
>>>> a MessageListener:
>>>>=20
>>>> =
failover://(tcp://localhost:19616?keepAlive=3Dtrue)?startupMaxReconnectAtt=
empts=3D5
>>>>=20
>>>> The message frequency is rather low (5-500 per hour) and can drop =
to
>>>> zero over multiple hours (during the night). Every now and then, =
the
>>>> MessageListener simply doesn't get any more messages and we have to
>>>> restart the application for a reconnect despite the failover =
protocol=20
>>>> (as seen above). We've tried various connection URI parameters but =
so
>>>> far, the issue keeps popping up every few weeks. I somehow doubt it =
has
>>>> to do with some timeout because, yesterday, it happened during the =
day
>>>> during normal business, not in the night after hours of inactivity. =
When
>>>> the problem happens, the message producer can still happily add new
>>>> messages which are then simply piled up.
>>>>=20
>>>> We first thought that the broker would stop accepting connections =
at
>>>> some point but we now have a monitoring agent for Nagios that =
regularly
>>>> tries to connect to ActiveMQ to check if anything is wrong on that =
side,
>>>> but that proved to be in vain. So, everything is solid on the =
broker
>>>> side.
>>>>=20
>>>> The client used to run ActiveMQ 5.3.0, too (just the
>>>> ActiveMQConnectionFactory, no broker). We also tried 5.5.1 on the =
client
>>>> side but nothing has changed.
>>>>=20
>>>> I was wondering if anyone has a good idea on this problem.
>>>>=20
>>>> Thanks a lot,
>>>> Jeremias Maerki
>>>=20
>>=20
>>=20
>>=20
>>=20
>=20

Torsten Mielke
torsten@fusesource.com
tmielke@blogspot.com