y are active.
We're rolling out 5.6.0 to the production environment soon. We'll see if
that changes anything.
Jeremias Maerki
On 04.06.2012 15:48:28 Raul Kripalani wrote:
> Definitely upgrade to 5.5.1 or later.
>
> What does your JMX instrumentation tell you when the problem
Thanks Raul, I'll check that next time it happens. Trying 5.6.0 is in
the pipeline. Will report back as soons as I know more. Could easily be
a couple of weeks until it happens again.
Jeremias Maerki
On 04.06.2012 15:48:28 Raul Kripalani wrote:
> Definitely upgrade to 5.5.1 or later.
&
'll take a peek
at 5.6.0 to see if it looks better there.
Jeremias Maerki
On 30.05.2012 11:30:04 Torsten Mielke wrote:
> Hello,
>
> 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
7;m probably
not the only one with this problem, although I couldn't find anything
related to that on the net.
Thanks,
Jeremias Maerki
On 25.05.2012 12:23:54 Jeremias Maerki wrote:
> Hi,
>
> I've got an ActiveMQ 5.3.0 broker running in one JVM.
>
>
>
has a good idea on this problem.
Thanks a lot,
Jeremias Maerki
