activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From SuoNayi <>
Subject Re:Re: Successfully delivered message ends up on DLQ
Date Wed, 13 Feb 2013 14:57:37 GMT
Hi,slave shoud continue trying to require the database row lock every x ms, here default value
for x is 1000ms.

Every try it just obtains a jdbc connection and close it finally, so it won't consumes many
connections(sessions in the database).
If there is connection leak problem then slave will consume many sessions(connects) to require
the row lock.
There are some relative jiras:

At 2013-02-13 19:01:04,jliezers <> wrote:
>I now believe the root cause is an our enthusiastic slave activemq consuming
>sessions attempting to acquire the lock on the ACTIVEMQ_LOCK table. We have
>a large number (100+) of unexpected sessions issuing UPDATE LOCK queries and
>then waiting. These are probably triggering the underlying connection resets
>as the max active sessions is only set to 200.
>View this message in context:
>Sent from the ActiveMQ - User mailing list archive at

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message