Hi Graham,
the warnings `No Expiry Address configured for queue...` or `No Expiry
Address configured for queue...` are often due to the lack of the default
address-setting (address-setting match="#") or to the mismatch from
`wildcard-addresses` node and the `address-settings` nodes (the `any-words
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
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
messagesK
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:Hea
Hi,
Firstly thank you and the team for Artemis. We have been using the fruits
of your labour from way back in HornetQ days. Thank you.
We have encountered a similar issue to the one described in:
https://issues.apache.org/jira/browse/ARTEMIS-2373
I do not have a reproducible test case but I will
