Hi Wendell,

I'm not sure if this is applicable to you situation but we encountered 
something remotely similar on Artemis and HornetQ:

1: We had "stuck" XA transactions on Apache Artemis. This is normal/expected 
behaviour when i.e. a client crashed during a two-phase commit. The transaction 
remains "in-doubt" until it is released.

2: On HornetQ we had consumers on queues with no actual client connected to 
them anymore. Message were delivered to those consumers and got "stuck" in a 
delivering state. When we restarted HornetQ the messages were "released" and 
new clients were able to consume them.
Cause was the connection-ttl (time-to-live) in the HornetQ configutation which 
was high, the default was overriden by us so we actually caused it ourself 😒. 
When a client was killed/stopped the connection was kept alive and the 
consumers where not removed, even though there was no client connected to it.
Stopping HornetQ removed the consumers.
We lowered the connection-ttl so consumers are removed earlier without a 
restart.

Best regards,
Jelmer






________________________________
From: Wendell Hatcher <[email protected]>
Sent: Friday, October 28, 2022 7:26 PM
To: [email protected] <[email protected]>
Subject: Re: jms messages keep getting stuck in our queues.

We are running 2 versions of Active AMQ  5.13.1 in one environment and
5.14.5 in 3 other environments.

On Fri, Oct 28, 2022 at 10:37 AM Clebert Suconic <[email protected]>
wrote:

> Start with the version please !?
> On Fri, Oct 28, 2022 at 9:48 AM Wendell Hatcher <
> [email protected]> wrote:
>
> > Hello, I am fairly knew to ActiveMQ troubleshooting message queues. We
> have
> > to restart our ActiveMQ services which connect to a backend muleESB
> almost
> > daily for certain queues. We try dumping the messages but the queues are
> > stuck and will not release the data. A restart of the services seems to
> > clear the queues but this occurs frequently.
> >
> >
> > Is there anything we can do to prevent this from happening?
> Troubleshooting
> > steps to take to narrow down why this keeps occurring as well?
> >
> >
> > -Wendell
> >
> --
> Clebert Suconic
>

Reply via email to