|
If you were logged in you would be able to see more operations.
|
|
|
|
In a simple test which pushes 300 messages Activemq only shows 180 messages when tried to look from JConsole using browse or browseAsTable method invocation. Same it true with using Camel route that uses BrowsableEndpoint to see browse the messages as camel exchange.
|
|
Description
|
In a simple test which pushes 300 messages Activemq only shows 180 messages when tried to look from JConsole using browse or browseAsTable method invocation. Same it true with using Camel route that uses BrowsableEndpoint to see browse the messages as camel exchange.
|
Show » |
|
Bug
Open
Major
ActiveMQ reports wrong number of messages with browseAsTable and browse operation in jconsole
there two interesting things going on in this example:
1. The the producer will hit memory limit used by cursor and will keep only part (181) of the messages in the memory. Only these messages, that are in the memory will be sent to the browser. The reason we can't send more messages is there's no space in memory to get them from the store.
2. Even if the memory limit is not hit, there's a limit of how much messages will be paged at once (and sent to the browser). And that number is 200 by default.
So, in order to have this test working, you have to have a setting like this:
<policyEntry queue=">" producerFlowControl="true" memoryLimit="2mb" maxPageSize="1000">
the first one ensures that all 300 messages sent can fit the memory and the page size to ensure that they can all be sent to the browser.