Po Cheung wrote:
>
>
> Po Cheung wrote:
>>
>> We got OutOfMemory errors on both the broker and client after
>> sending/receiving 600K messages to persistent queues with transactions.
>> The memory graph below shows the heap usage of the broker growing
>
e a mix of the journal and kaha - I'll try document it soon!
>
> cheers,
>
> Rob
>
> On 21 Mar 2007, at 19:12, Po Cheung wrote:
>
>>
>> ActiveMQ was consuming 100% cpu for over 12 hours after the
>> restart. Here is
>> a partial thread dum
Po Cheung wrote:
>
> We got OutOfMemory errors on both the broker and client after
> sending/receiving 600K messages to persistent queues with transactions.
> The memory graph below shows the heap usage of the broker growing
> gradually. Max heap size is 512MB. UsageManager i
We got OutOfMemory errors on both the broker and client after
sending/receiving 600K messages to persistent queues with transactions. The
memory graph below shows the heap usage of the broker growing gradually.
Max heap size is 512MB. UsageManager is also at 512MB (will that cause a
problem? s
ice.start(BrokerService.java:394)
. . .
Po
Po Cheung wrote:
>
> ActiveMQ was restarted but did not come up successfully. Clients could
> not connect to it.
>
> 2007-03-16 14:43:11,026 [WrapperSimpleAppMain] INFO
> (BrokerService.java:505) - ActiveMQ 4.1-SNAPSHOT JMS Mess
ActiveMQ was restarted but did not come up successfully. Clients could not
connect to it.
2007-03-16 14:43:11,026 [WrapperSimpleAppMain] INFO
(BrokerService.java:505) - ActiveMQ 4.1-SNAPSHOT JMS Message Broker
(localhost) is starting
2007-03-16 14:43:11,030 [WrapperSimpleAppMain] INFO
(BrokerS
I am seeing a queue being blocked in both ActiveMQMessageProducer.send() and
ActiveMQMessageConsumer.close() and no more messages can be produced or
consumed. The test case involved a client sending a single message to a
queue every 10 minutes. Another client consumed the message and produced a
Here is the missing thread dump for ActiveMQMessageProducer.send in the
original post:
"jmsConnector.jmsConnector.dispatchers.dispatcher.8" prio=1 tid=0xbf91bcc0
nid=0xab156bb0 [EMAIL PROTECTED] in Object.wait() [ab155000..ab156170]
at java.lang.Object.wait(Native Method)
- waiting on <
I am seeing a queue being blocked in both ActiveMQMessageProducer.send() and
ActiveMQMessageConsumer.close() and no more messages can be produced or
consumed. The test case involved a client sending a single message to a
queue every 10 minutes. Another client consumed the message and produced a