We had this problem as well. We resolved it by sending a DISCONNECT command
before our stomp client quits.If you don't send the DISCONNECT command,
the connections will continue to add up in ActiveMQ until it crashes with
the error you got. This behavior seems to have started with ActiveMQ 4
The number of threads is increasing constantly.
Now I have.
Live Theads 400. Daemon threads 388
Peak 401. Total started 814.
Why is that? I am sending and consuming message every minute by stomp
jzhang1 wrote:
>
> Yes. I am jmx monitoring. Upload the screenshot
>
>
>
>
>
>
>
> r
Yes. I am jmx monitoring. Upload the screenshot
rajdavies wrote:
>
> can you monitor the server using jmx - to see how many threads/
> sockets are being used ?
>
> On Jul 17, 2007, at 8:36 PM, jzhang1 wrote:
>
>>
>> ActiveMQ gurus
>>
>> ActiveMQ version 4.1.0. It always crash after runi
can you monitor the server using jmx - to see how many threads/
sockets are being used ?
On Jul 17, 2007, at 8:36 PM, jzhang1 wrote:
ActiveMQ gurus
ActiveMQ version 4.1.0. It always crash after runing about 8 hours. I
changed java heap and stack memory -Xmx -Xss. But it never helps. The
mac
ActiveMQ gurus
ActiveMQ version 4.1.0. It always crash after runing about 8 hours. I
changed java heap and stack memory -Xmx -Xss. But it never helps. The
machine is 4G memory and 4 processors. The MQ messages arrive and consume
every minute. No message accumulation in the queue.
Exception in
