Hi Matt,
Appreciate the response. We'll keep digging on our side and loop back if
we're able to provide anything more concrete.
Regards,
Derek Zhang
On Fri, 26 Apr 2024 at 13:31, Matt Pavlovich wrote:
> Hi Derek-
>
> No known report with a similar scenario. Without a specific exception
>
Hi Derek-
No known report with a similar scenario. Without a specific exception message
or reproducible use case, this isn’t something that the Apache community is
able to effectively support given all the possible factors in your
organizations specific environment.
If you are able to
Thanks Justin,
Yes, we realize that we're not doing ourselves any favours by staying on
5.15.x in this case as there have been numerous improvements to ActiveMQ
since.
Because this issue is very sporadic and hard to reproduce, we're mostly
curious if anyone else has seen this in the past at all.
I can't comment regarding your specific issue, but it's worth noting that
5.15.x is no longer actively maintained. It may be worth upgrading to the
latest 5.18.x version or perhaps even 6.x.
Justin
On Fri, Apr 26, 2024 at 2:26 PM Derek Zhang wrote:
> Hello ActiveMQ Classic community,
>
> We
Hello ActiveMQ Classic community,
We recently saw a broker running 5.15.16 getting stuck during recovery.
When ActiveMQ was started, we saw the following log messages and then
nothing else:
2024-04-18 17:21:52,670 | INFO | Refreshing
org.apache.activemq.xbean.XBeanBrokerFactory$1@25bbe1b6:
