Hi, Tim
Happy to communicate with u again.
I pasted the exception message on my first message.
It didn't show any detailed or explicit hint.
There's not any valuable info about how to deal with the problem.
No any message is about Brokers.
I only set the value "nested.wireFormat.maxInactivityDur
when ActiveMQ will invoke the close() method
implicitly or explicitly.
Thanks.
Chester
chester_zh...@sina.com
From: Tim Bain [via ActiveMQ]
Date: 2017-05-01 04:20
To: Chester_Zheng
Subject: Re: The connection is already closed
The close() methods you referenced are on the factory, while the error
messa
will invoke the close() method implicitly
or explicitly.
Thanks.
Chester
chester_zh...@sina.com
From: Tim Bain [via ActiveMQ]
Date: 2017-05-01 04:20
To: Chester_Zheng
Subject: Re: The connection is already closed
The close() methods you referenced are on the factory, while the error
messa
The close() methods you referenced are on the factory, while the error
message you're getting is about the close() method of the connections
returned by the factory.
If you can reproduce the problem in a non-operational environment, attach a
debugger and set a breakpoint on the connection's close(
