How are you able to tell that a single call to updateIndex() is taking 3.5
minutes? It's not possible to determine that from thread dumps alone, so
what other tool are you using to prove that assertion?
A profiler such as JVisualVM would help you determine where precisely the
broker is spending i
Is hdp132 the master or the slave? And what URI does your client use to
connect?
Do you see that message once, or six times?
On Apr 8, 2016 12:32 PM, "Natarajan, Rajeswari"
wrote:
> Thanks Tim for the detailed email. When I do failover I see below
> exception in our app logs.
>
> org.apache.ac
Hopefully resolving the errors you see when setting the prefetch size will
fix your problem. If not, let us know what the behavior is with a prefetch
value of 1, 2, and 10, once that works.
On Apr 8, 2016 9:28 AM, "Michele" wrote:
> Hi Tim,
>
> exactly... According to http://camel.apache.org/jms
Looks like your attachment from YourKit was stripped off.
But your suggestion seems like a reasonable improvement; submit a JIRA
enhancement request. Even better, a patch or a pull request!
On Apr 9, 2016 11:51 AM, "Martin Lichtin" wrote:
With a test sending 5000 messages to a queue, I see heav
With a test sending 5000 messages to a queue, I see heavy CPU use on the broker
side (v 5.12.2).
Using Yourkit it shows that the hot spot methods are
FilePendingMessageCursor.isEmpty() iterates over in-memory messages and
therefore (as it is a prioritized queue) uses PrioritizedPendingListIte
