]
Tim Fox closed JBMESSAGING-1018.
--------------------------------
Resolution: Out of Date
Possibly fix timeout due to bug in remoting that may allow clients to
hang forever.
-----------------------------------------------------------------------------------
Key: JBMESSAGING-1018
URL:
http://jira.jboss.com/jira/browse/JBMESSAGING-1018
Project: JBoss Messaging
Issue Type: Feature Request
Components: JMS Remoting
Affects Versions: 1.3.0.GA
Reporter: Jay Howell
Assigned To: Tim Fox
Fix For: Unscheduled
This goes back to JBMESSAGING-171, when we changed the timeout on the bisocket to 0.
That would have meant that it would wait forever which is what we want. There is now a
bug in remoting that if this is set to 0 and the client is unreachable, then it is
possible that it will hang. We may have one case of this now, but it is still unverified.
The remoting bug is JBREM-767. This is fixed in the 2.4 beta of remoting, but it may
present a problem before we can integrate that version in. We may want to consider
changing this to a high number, so it doesn't timeout easily, but so it will timeout.
Just want to put it up for concideration. The other route is to get the remoting team
to put out another sp version with. They could put it in 2.2.0.SP4_CP02, but that will
only go out as part of the Platform 4.2 CR release, so we may want to ask them to put it
out as an 2.2.0SP5, so it will go into general population where Messaging has alot of
customers.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: