Paul French wrote:
>
> Okay, I switched on garbage collection output using the flag -verbosegc and
> the Aysnc failure on the client does coincide with a FULL GC event. On my
> client system I am close to the max heap size nearly all the time. The FULL
> GC takes about 25 seconds to complete. All
So yes - its looking like the connection is being disconnected due to
inactivity. You could increase the inactivity timeout to something
much bigger (or even disable it) to avoid the broker closing your
connections.
Whether the connection is closed or not, with failover: all
sessions/producers/co
Okay, I switched on garbage collection output using the flag -verbosegc and
the Aysnc failure on the client does coincide with a FULL GC event. On my
client system I am close to the max heap size nearly all the time. The FULL
GC takes about 25 seconds to complete. All client threads are suspended
Hold fire on this one, it could be a garbage collection problem causing the
long pause. I've got parallel garbage collection switched on so I would not
expect all threads to stop so it is a strange one.
Paul French wrote:
>
> For me this is a continuation of.
>
> http://ww
For me this is a continuation of.
http://www.nabble.com/Async-Exception%3A-Broken-Pipe-t3160498s2354.html#a8765808
...but I have now taking the advice from the above post and have refined the
problem I am having.
Environment
I am now using the latest 4.2 snapshot as requested (29th Jan 200
