We are using ActiveMQ version 5.9.0 and using the Failover Transport with a
single host and suspect that a JMS connection failure
(transportInterrupted)/re-connection (transportResumed) is sometimes causing
a thread which is dispatching a message to the Broker to become stuck/hung.
Once this occur
I'm new to ActiveMQ so please bear with me if my question seem dumb :D
I have installed activemq on a CentOS machine and I'm connecting to it for
writing to the qeueue and consuming from the queue through the admin user
(which I dont think its the ideal way). I'm wondering if I can create a user
f
Note, BTW, that this doesn't include the time the message is unconsumed in
the consumer' s prefetch buffer.
On May 10, 2016 6:56 AM, "Tim Bain" wrote:
> SUM(DispatchTime - EnqueueTime)/COUNT
>
> The computation is done here:
> http://grepcode.com/file/repo1.maven.org/maven2/org.apache.activemq/ac
On 05/09/2016 09:11 PM, sabyasachi087 wrote:
I need to know the exact process involved in calculation of avg enqueue
time??
--
View this message in context:
http://activemq.2283324.n4.nabble.com/How-activemq-statistics-plugin-calculates-averageEnqueueTime-and-other-attributes-tp4711738p471177
SUM(DispatchTime - EnqueueTime)/COUNT
The computation is done here:
http://grepcode.com/file/repo1.maven.org/maven2/org.apache.activemq/activemq-broker/5.11.1/org/apache/activemq/broker/region/RegionBroker.java#RegionBroker.preProcessDispatch%28org.apache.activemq.command.MessageDispatch%29
On May
