If there is a blocked thread somehow, your stack trace didn't indicate any
Jetty thread issues.
It did indicate some problems with the mysql connection, however.
On Wed, Jul 16, 2014 at 1:07 AM, Manu wrote:
> Any clue ?
>
>
>
> On Fri, Jul 4, 2014 at 9:52 AM, Manu wrote:
>
> > No that large :
Any clue ?
On Fri, Jul 4, 2014 at 9:52 AM, Manu wrote:
> No that large : 360 messages of average size of less than 1Ko.
> I did not check the heap at the time of the event. I'll take a look at
> those next time ...
>
> But do you think Jetty can have keep ActiveMq from shutting down ?
>
>
>
>
No that large : 360 messages of average size of less than 1Ko.
I did not check the heap at the time of the event. I'll take a look at
those next time ...
But do you think Jetty can have keep ActiveMq from shutting down ?
On Thu, Jul 3, 2014 at 5:58 PM, Christian Posta
wrote:
> How large were
How large were these messages you were trying to browse, and how much
broker memory and JVM heap was available?
On Thu, Jul 3, 2014 at 3:07 AM, Manu wrote:
> Hi there,
>
> We're facing a strange problem with our master slave configuration.
> We are using ActiveMQ 5.8.0 with a master/slave confi
Hi there,
We're facing a strange problem with our master slave configuration.
We are using ActiveMQ 5.8.0 with a master/slave configuration with a mysql
persistent storage.
This morning we were browsing the activemq admin console
(http://:8161/admin/queues.jsp)
and wanted to browse 360 messages t
