Close timeout handling has been fixed up a fair bit with issue:
https://issues.apache.org/jira/browse/QPIDJMS-228
On 11/25/2016 11:04 AM, Robbie Gemmell wrote:
"I also think I see an issue with the closeTimeout handling in that in
one place it seems likely to be using the requestTimeout value
instead. Need to investigate that further."
Though in my attemps that didnt actually matter and the close
completed fine if the network dropped and no response could be
received (or was ever sent). As I say, needs more investigation.
On 25 November 2016 at 15:49, DraCzech <dracz...@gmail.com> wrote:
I'll try to find a way of preventing this problem from happening. (Though I'm
not sure how to do that properly at the moment.)
But how do you explain unlimited waiting for Close frame response as shown
in my previous post?
DraCzech wrote
2016-11-24 16:41:45.202589 [19105288:0] -> Close{error=null}
on network lost vs.
2016-11-24 16:51:31.027968 [18734493:0] -> Close{error=null}
2016-11-24 16:51:31.977722 [18734493:0] <- Close{error=null}
Shouldn't some timeout throw an exception or so?
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Qpid-JMS-client-JmsConnection-close-hangs-tp7654565p7654872.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
