Hi Moshe,
Looks like the problem is about how you consume messages. Instead of using
regular subscribe approach, you retain messages using queue browser:
QueueBrowser queueBrowser = consumerSession.createBrowser(queue);
Enumeration msgs = queueBrowser.getEnumeration();
This is wrong. Queue brows
XPath support is not documented anywhere that I know of - probably because
it was never implemented. Implementing such support would be a feature
request.
At the moment, filters only work on the message headers/properties.
If you want to filter with XPath on the body of the message your only
opt
Filed https://issues.apache.org/jira/browse/ARTEMIS-2132
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Hi,
>From the side, it does look like pending messages accumulated in memory
because of a slow or blocked subscriber. Since you have heap dump, you
should look at this specific TopicSubscription object just to make sure you
don't have actually a consumer subscribed to some of your topics, but not
Hi all,
- Ideal Use Case
We'd like to ensure high availability using failover, and then
normalization of the environment using failback once the server which was
shut down is back up.
- Context and Environment
* We have two brokers running on two seperate servers, set up in a
cluster with
