thank you for the explanation.
well, right now I have around 500+ destinations (queues and topics). This is
about to grow further, as my number of karaf instances (with camel routes)
accessing the broker grows. Alongside scaling, as many karaf instances, I
also need to ensure that my messages are
with optimizedDispatch=true, the queue dispatch thread is redundant
(the thread that reads a message does the dispatch) and does not get
to service a browse repeatedly.
it turns a browse into a one shot operation.
The benefits of optimizedDispatch=true are really only apparent with
straight through
Hi again @gtully,
I have a query again.
What if I do not use optimizedDispatch? How does optimizedDispatch help in
scaling. I guess, it does by limiting the message window size. But,
alternately, does it affect the broker's performance?
Any clarification on this would be very helpful.
Regards,
Hi again:
so, does that also mean that my broker will be able to fetch upto 4000
messages at a time? If so, I guess I will run out of connections, right?
Or, will that be managed by ActiveMQ? I will try to play with these settings
and get back.
Regards,
Cooshal.
--
Sent from: http://activemq.
Hi:
ahh ok. then that was caused by optimizedDispatch, right?
Thanks for the clarification.
Regards,
Cooshal.
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
there is a policyEntry maxBrowsePageSize with default value 400,
increase that value to see a different result.
`
On Mon, 24 Jun 2019 at 16:11, cooshal wrote:
>
> Hi again:
>
> I checked further stuffs on this issue, and I think I am not able to fetch
> JMS Messages > 400, because of optimizedDi
Hi again:
I checked further stuffs on this issue, and I think I am not able to fetch
JMS Messages > 400, because of optimizedDispatch="true" in the policyEntry
configuration of the broker. I had it as below:
``
This was a recommended setting for scaling broker service.
Could it be because of th
Hi again:
I have one weird update to this issue.
I am using 5.15.8 locally, and 5.15.4 in production.
Strangely, I can get the actual messages count in the production
environment, which was definitely more than 400 (e.g. 3500).
Does any broker specific config parameter lets us retrieve messages
Hi Tim and JB:
thank you.
I will check this out. Before using JMS API, I had tried Jolokia, and I
faced similar issues, so I had posted a question on StackOverflow about it
(https://stackoverflow.com/questions/55708890/is-it-possible-to-retrieve-more-than-400-messages-from-activemq-queue-via-jolo
Hi,
Just use JMX on the destination, you have lot of details (QueueSize,
cursor, memory, etc).
You can use Decanter to collect the JMX metrics.
Regards
JB
On 19/06/2019 19:18, cooshal wrote:
> Hi:
>
> thank you for the clarification.
>
> Is there a way to retrieve the queue stats? I wanted to
On 6/19/19 1:18 PM, cooshal wrote:
Hi:
thank you for the clarification.
Is there a way to retrieve the queue stats? I wanted to retrieve the number
of messages, pending messages, etc. similar to those shown in activemq
console.
The only really reliable means would be to use JMX and ask the MB
Hi:
thank you for the clarification.
Is there a way to retrieve the queue stats? I wanted to retrieve the number
of messages, pending messages, etc. similar to those shown in activemq
console.
Regards,
Cooshal.
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
On 6/19/19 12:13 PM, cooshal wrote:
Hi:
I am using ActiveMQ version 5.15.8
I have the following code fragment, which is basically there to count the
number of messages in a particular queue (here, it is tst.errors)
brokerConnection = connectionFactory.createConnection();
session = this.createS
Hi:
I am using ActiveMQ version 5.15.8
I have the following code fragment, which is basically there to count the
number of messages in a particular queue (here, it is tst.errors)
brokerConnection = connectionFactory.createConnection();
session = this.createSession(brokerConnection);
brokerConnec
14 matches
Mail list logo
