If you use failover transport, there is an timeout option that can be enabled
to address the issue.
see http://activemq.apache.org/failover-transport-reference.html
At 2013-07-16 20:32:54,lzr wrote:
>I found the issue just this time. It worked fine for about two month with the
>ActiveMQ M/S
I found the issue just this time. It worked fine for about two month with the
ActiveMQ M/S cluster.
I've thought of the network glitch; What I feel strange most is there is no any
error/exception on both the ActiveMQ client side and server side.
I went through the related codes and found there is
Is this something that happens all the time? Maybe your network had a
glitch and didn't deliver the response back to the client.
On Tue, Jul 16, 2013 at 8:18 AM, lzr wrote:
> I just check the configuration file, actually I've disabled the flow
> control:
>
>
>
>
>
I just check the configuration file, actually I've disabled the flow control:
Yes, on the first time PFC kicked in you would see the log messages. Not on
subsequent times.
On Tue, Jul 16, 2013 at 8:01 AM, lzr wrote:
> Based on my experiences if the issue caused by the producer flow control
> configuration, the logs will have some warning messages, right? In fact I
> didn
This means the client didn't' receive a response from the broker.
Did the broker producer flow control this client? ie, was the destination
to which the client sending full?
On Tue, Jul 16, 2013 at 7:23 AM, lzr wrote:
> Dear all,
>
>
> I found a one of the ActiveMQ thread got stuck unexpectedly
