Acking happens as needed.
my page size is set to
I have 923 messages on the queue. Any other ideas?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Issue-with-MessageConsumer-and-MessageSelector-tp4704870p4704939.html
Sent from the ActiveMQ - User mailing list archive
To acheive the split between "high priority" and "low priority" without
starving the low-priority messages, I recommend:
1. use separate queues to split the priorities
2. either use dedicated consumers for the low priorities that do not take
resources away from the higher priorities, or use some f
There are two things that happen with message groups that makes them a poor
match for use with selectors.
First, the default implementation of message groups uses "buckets" of
assignments for groups-to-consumers. This means that multiple groups
actually get assigned to the same consumer because t
Note that I have personally seen the HTTP transport consuming significant CPU
resources in the past. Be sure to measure performance and watch CPU
utilization. IIRC that's because the implementation frequently polls.
I recommend looking to an alternate approach. One I've implemented with
great r
Two things to look at. As mentioned above, not ack'ing is one of them. If
the session is setup to auto-ack, then that's not the issue. If the session
is set to client-ack or transacted, then it needs to ack the messages or the
queue will eventually fill up.
Another possibility - look at the que
Also, I am not acking the messages as they come through.
Here is what I also notice.
I bring up a MessageListener(no ack) and then bring it down. Now I look for
my message on the Queue an I find it, copy it into a new message and queue
it. I remove the old message.
I now try to do the same thing
Hi we use the master-slave cluster,using Apache ZooKeeper to pick a master,
we have three replications(192.168.1.98,99,116),we have one master ,two
slaves,and three zookeepers(192.168.103,104,105) ,one of the configurations of
replications is as follows:
zkAd
Hi
We use the master-slave cluster,using Apache ZooKeeper to pick a master, we
have three replications(192.168.1.98,99,116),we have one master ,two
slaves,and three zookeepers(192.168.103,104,105) ,one of the configurations
of replications is as follows:
zkAddress
Hi Tim,
Thanks for the feedback.
The idea with the low and normal priority message separation arouse as a
consequence of the main business process in the application.
The application works in such a way that it is constantly fed by the normal
priority events, for which the processing time is of
Hi,
I've recently implemented an ActiveMQ installation using Zookeeper as
cluster manager.
Our setup is:
12 contributors writing to two Virtual topics
3 Queues (each with 12 consumers)
Approx. 120 messages per second
The setup of activemq.xml is fairly default, here are a few changes;
http://
10 matches
Mail list logo
