Heap dumps are useful in pretty limited circumstances (of which this is not
one). What I was asking for is a thread dump, which will give the current
stack trace for every thread in the JVM, so we can see where the failover
transport is getting stuck.

Tim

On Jul 26, 2017 12:25 AM, "akpuvvada" <[email protected]> wrote:

> heapdump-1501050187914.zip
> <http://activemq.2283324.n4.nabble.com/file/n4728904/
> heapdump-1501050187914.zip>
>
> Hi Tim,
> Please find attached the Head Dump.
>
> I am not sure how to read this, so, no idea what it is saying.
>
> Let us know if you find anything.
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.
> nabble.com/Active-MQ-Master-Slave-Config-Not-working-
> tp4728550p4728904.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>

Reply via email to