Thanks for the detailed response!
Unfortunately I don't know when the out of memory error happened. My logs
were full of them. Messages started appearing
in the DLQ about 21:00, and the logs with the OOM start at around 05:00 the
day after.
On the producer end, I connect to ActiveMQ using a Acti
Thanks for the detailed response!
Unfortunately I don't know when the out of memory error happened. My logs
were full of them. Messages started appearing
in the DLQ about 21:00, and the logs with the OOM start at around 05:00 the
day after.
On the producer end, I connect to ActiveMQ using a Acti
Thanks Gary. I was convinced that the default configuration did not contain
any of the message-discarding options from the slow consumers page I linked
to; I'm not sure where I got that idea. But that explanation makes more
sense than my wild theory about the no-consumer behavior of statically
incl
dlqDeliveryFailureCause java.lang.Throwable: TopicSubDiscard.
ID:localhost->fmiuseastp01-63022-1486246061090-100948:1:1:2
The cause indicates the a subscriber is full and has been configured to
discard messages[1]. See policyEntry from the default config [2]
https://github.com/apache/activemq/blo
Thanks for the detailed response!
Unfortunately I don't know when the out of memory error happened. My logs
were full of them. Messages started appearing
in the DLQ about 21:00, and the logs with the OOM start at around 05:00 the
day after.
On the producer end, I connect to ActiveMQ using a Acti
First, the categorical statement is that when you hit an Out of memory
error, you have no guarantee that your application is still in a valid
state, so you should terminate the JVM and restart. So my first question
is, does this happen when you haven't run the JVM out of heap space? If
not, the beh
I also got these messages when I had a network connector setup. The setup
seems similar to OP, where we had a message configured to be sent via a
staticallyIncludedDestinations block, and it ended up in the DLQ with
"TopicSubDiscard". Here's a full dump of one of the messages that ended up
in the D
This tells you that the messages were discarded by ActiveMQ because they
had expired. Are your producers setting a time to live when sending
messages?
Tim
On Fri, Sep 15, 2017 at 5:42 PM, mtod wrote:
> I'm running ActiveMQ 5.10.0 with an embedded camel route. It's been running
> fine until we c
I'm running ActiveMQ 5.10.0 with an embedded camel route. It's been running
fine until we connected the master to an instance 5.14.5.
5.10.0 Network Connector:
