Hi,
Have done some more investigations into the heap dump.
All 1.2m messages on the internal queue were addressed to a specific
jms.topic.
There were many other producers publishing to the same topic at the time
and there was no apparent issue with the topic consumer.
A question:
Should we assign a Dead Letter address for the internal
$.artemis.internal.sf.... queues? I am confused on whether we should or
should not do that.
Really appreciate any help you can give me on this.
Many thanks
Graham
On Mon, 30 Mar 2020 at 23:08, Graham Stewart <grahamdstew...@gmail.com>
wrote:
> Thanks Domenico,
>
> We have a heap dump from when this happened last week - it's large - 8GB.
>
> We can see the internal queue that blew up was
>
>
> $.artemis.internal.sf.cluster-prodemea-r186951.39.7adc9da9-6c30-11ea-b3c0-0050568f93e5
>
>
> From the heap dump that QueueImpl has
>
> messagesReplaced 0
>
> messagesKilled 0
>
> messagesExpired 0
>
> ackAttempts 17215914
> messagesAcknowleged 17215914
> messagesAdded 18437336
>
> queueMemorySize 108598463
>
> Can you let me know what other details would be useful? Can run some OQL
> against the dump to pull things out if that would help.
> I tried to attach a thread dump - but it exceeds the mailing list limit.
> Would it be useful?
>
> Thanks
>
> Graham
>
>
> On Mon, 30 Mar 2020 at 21:51, brusdev <bruscin...@gmail.com> wrote:
>
>> Hi Graham,
>>
>> can you enable the dumping of the java heap when a
>> java.lang.OutOfMemoryError exception is thrown and send a screenshot or
>> summary?
>>
>> To enable the heap dump, you could uncomment the following line in
>> `artemis.profile` file:
>> # JAVA_ARGS="$JAVA_ARGS -XX:+HeapDumpOnOutOfMemoryError
>> -XX:HeapDumpPath=${ARTEMIS_OOME_DUMP}"
>>
>> Thanks,
>> Domenico
>>
>>
>>
>> --
>> Sent from:
>> http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
>>
>
