[JBoss JIRA] Created: (JBREM-767) Avoid deadlock in callback BisocketClientInvoker when timeout == 0
12:26 p.m.
Avoid deadlock in callback BisocketClientInvoker when timeout == 0
------------------------------------------------------------------
Key: JBREM-767
URL: http://jira.jboss.com/jira/browse/JBREM-767
Project: JBoss Remoting
Issue Type: Task
Security Level: Public (Everyone can see)
Affects Versions: 2.4.0.Beta1 (Pinto)
Reporter: Ron Sigal
Assigned To: Ron Sigal
Fix For: 2.4.0.Beta1 (Pinto)
If timeout == 0 then
org.jboss.remoting.transport.bisocket.BisocketClientInvoker.createSocket() can hang
forever if the client side is unavailable.
One fix is to not set timeout to 0, but currently the timeout value is inherited from the
server invoker, for which timeout == 0 might be appropriate. One solution is to implement
a separate timeout parameter for callback client invokers (JBREM-765).
Another fix is for PingTimeTask to notify a thread waiting in createSocket() when an
attempt to send a PING to the client fails.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:31 p.m.
New subject: [JBoss JIRA] Updated: (JBREM-767) Avoid deadlock in callback BisocketClientInvoker when timeout == 0
[ http://jira.jboss.com/jira/browse/JBREM-767?page=all ]
Ron Sigal updated JBREM-767:
----------------------------
Fix Version/s: 2.2.1.SP1
2.2.0.SP4_CP02
Affects Version/s: 2.2.1.GA
2.2.1.SP1
Avoid deadlock in callback BisocketClientInvoker when timeout == 0
------------------------------------------------------------------
Key: JBREM-767
URL: http://jira.jboss.com/jira/browse/JBREM-767
Project: JBoss Remoting
Issue Type: Task
Security Level: Public(Everyone can see)
Affects Versions: 2.4.0.Beta1 (Pinto), 2.2.1.GA, 2.2.1.SP1
Reporter: Ron Sigal
Assigned To: Ron Sigal
Fix For: 2.4.0.Beta1 (Pinto), 2.2.0.SP4_CP02, 2.2.1.SP1
If timeout == 0 then
org.jboss.remoting.transport.bisocket.BisocketClientInvoker.createSocket() can hang
forever if the client side is unavailable.
One fix is to not set timeout to 0, but currently the timeout value is inherited from the
server invoker, for which timeout == 0 might be appropriate. One solution is to implement
a separate timeout parameter for callback client invokers (JBREM-765).
Another fix is for PingTimeTask to notify a thread waiting in createSocket() when an
attempt to send a PING to the client fails.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:16 p.m.
New subject: [JBoss JIRA] Commented: (JBREM-767) Avoid deadlock in callback BisocketClientInvoker when timeout == 0
[ http://jira.jboss.com/jira/browse/JBREM-767?page=comments#action_12371144 ]
Ron Sigal commented on JBREM-767:
---------------------------------
One fix for this issue is to move network i/o from the BisocketClientInvoker constructor
to BisocketClientInvoker.handleCconnect() - JBREM-787.
Another fix is to have BisocketClientInvoker.handleDisconnect() wake up any threads
waiting in BisocketClientInvoker.createSocket().
The fix for the latter has been applied to branch remoting_2_2_0_GA.
Unit test: org.jboss.test.remoting.transport.bisocket.CallbackDisconnectTestCase.
Avoid deadlock in callback BisocketClientInvoker when timeout == 0
------------------------------------------------------------------
Key: JBREM-767
URL: http://jira.jboss.com/jira/browse/JBREM-767
Project: JBoss Remoting
Issue Type: Task
Security Level: Public(Everyone can see)
Affects Versions: 2.4.0.Beta1 (Pinto), 2.2.1.GA, 2.2.1.SP1
Reporter: Ron Sigal
Assigned To: Ron Sigal
Fix For: 2.4.0.Beta1 (Pinto), 2.2.0.SP4_CP02, 2.2.1.SP1
If timeout == 0 then
org.jboss.remoting.transport.bisocket.BisocketClientInvoker.createSocket() can hang
forever if the client side is unavailable.
One fix is to not set timeout to 0, but currently the timeout value is inherited from the
server invoker, for which timeout == 0 might be appropriate. One solution is to implement
a separate timeout parameter for callback client invokers (JBREM-765).
Another fix is for PingTimeTask to notify a thread waiting in createSocket() when an
attempt to send a PING to the client fails.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:25 p.m.
New subject: [JBoss JIRA] Commented: (JBREM-767) Avoid deadlock in callback BisocketClientInvoker when timeout == 0
[ http://jira.jboss.com/jira/browse/JBREM-767?page=comments#action_12371162 ]
Ron Sigal commented on JBREM-767:
---------------------------------
Another fix is to allow a separately configurable timeout value for callback clients
(JBREM-765). That feature has been implemented on the remoting_2_2_0_GA branch.
Avoid deadlock in callback BisocketClientInvoker when timeout == 0
------------------------------------------------------------------
Key: JBREM-767
URL: http://jira.jboss.com/jira/browse/JBREM-767
Project: JBoss Remoting
Issue Type: Task
Security Level: Public(Everyone can see)
Affects Versions: 2.4.0.Beta1 (Pinto), 2.2.1.GA, 2.2.1.SP1
Reporter: Ron Sigal
Assigned To: Ron Sigal
Fix For: 2.4.0.Beta1 (Pinto), 2.2.0.SP4_CP02, 2.2.1.SP1
If timeout == 0 then
org.jboss.remoting.transport.bisocket.BisocketClientInvoker.createSocket() can hang
forever if the client side is unavailable.
One fix is to not set timeout to 0, but currently the timeout value is inherited from the
server invoker, for which timeout == 0 might be appropriate. One solution is to implement
a separate timeout parameter for callback client invokers (JBREM-765).
Another fix is for PingTimeTask to notify a thread waiting in createSocket() when an
attempt to send a PING to the client fails.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:31 p.m.
New subject: [JBoss JIRA] Updated: (JBREM-767) Avoid deadlock in callback BisocketClientInvoker when timeout == 0
[ http://jira.jboss.com/jira/browse/JBREM-767?page=all ]
Ron Sigal updated JBREM-767:
----------------------------
Fix Version/s: 2.2.2.GA
2.4.0.CR1 (Pinto)
(was: 2.4.0.Beta1 (Pinto))
(was: 2.2.0.SP4_CP02)
(was: 2.2.1.SP1)
Affects Version/s: 2.2.0.SP4
(was: 2.2.1.SP1)
Avoid deadlock in callback BisocketClientInvoker when timeout == 0
------------------------------------------------------------------
Key: JBREM-767
URL: http://jira.jboss.com/jira/browse/JBREM-767
Project: JBoss Remoting
Issue Type: Task
Security Level: Public(Everyone can see)
Affects Versions: 2.4.0.Beta1 (Pinto), 2.2.0.SP4, 2.2.1.GA
Reporter: Ron Sigal
Assigned To: Ron Sigal
Fix For: 2.4.0.CR1 (Pinto), 2.2.2.GA
If timeout == 0 then
org.jboss.remoting.transport.bisocket.BisocketClientInvoker.createSocket() can hang
forever if the client side is unavailable.
One fix is to not set timeout to 0, but currently the timeout value is inherited from the
server invoker, for which timeout == 0 might be appropriate. One solution is to implement
a separate timeout parameter for callback client invokers (JBREM-765).
Another fix is for PingTimeTask to notify a thread waiting in createSocket() when an
attempt to send a PING to the client fails.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:51 p.m.
New subject: [JBoss JIRA] Updated: (JBREM-767) Avoid deadlock in callback BisocketClientInvoker when timeout == 0
[ http://jira.jboss.com/jira/browse/JBREM-767?page=all ]
Ron Sigal updated JBREM-767:
----------------------------
Fix Version/s: 2.4.0.Beta1 (Pinto)
(was: 2.4.0.CR1 (Pinto))
Avoid deadlock in callback BisocketClientInvoker when timeout == 0
------------------------------------------------------------------
Key: JBREM-767
URL: http://jira.jboss.com/jira/browse/JBREM-767
Project: JBoss Remoting
Issue Type: Task
Security Level: Public(Everyone can see)
Affects Versions: 2.4.0.Beta1 (Pinto), 2.2.0.SP4, 2.2.1.GA
Reporter: Ron Sigal
Assigned To: Ron Sigal
Fix For: 2.4.0.Beta1 (Pinto), 2.2.2.GA
If timeout == 0 then
org.jboss.remoting.transport.bisocket.BisocketClientInvoker.createSocket() can hang
forever if the client side is unavailable.
One fix is to not set timeout to 0, but currently the timeout value is inherited from the
server invoker, for which timeout == 0 might be appropriate. One solution is to implement
a separate timeout parameter for callback client invokers (JBREM-765).
Another fix is for PingTimeTask to notify a thread waiting in createSocket() when an
attempt to send a PING to the client fails.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:59 p.m.
New subject: [JBoss JIRA] Closed: (JBREM-767) Avoid deadlock in callback BisocketClientInvoker when timeout == 0
[ http://jira.jboss.com/jira/browse/JBREM-767?page=all ]
Ron Sigal closed JBREM-767.
---------------------------
Resolution: Done
Fixes for JBREM-765, JBREM-787, and having BisocketClientInvoker.handleDisconnect() wake
up any threads waiting in BisocketClientInvoker.createSocket() have been applied to branch
remoting_2_x.
The proposed fix "Another fix is for PingTimeTask to notify a thread waiting in
createSocket() when an attempt to send a PING to the client fails." has not been
implemented, since it adds a function for which PingTimerTask was not designed.
The unit test is passing on cruisecontrol.
Avoid deadlock in callback BisocketClientInvoker when timeout == 0
------------------------------------------------------------------
Key: JBREM-767
URL: http://jira.jboss.com/jira/browse/JBREM-767
Project: JBoss Remoting
Issue Type: Task
Security Level: Public(Everyone can see)
Affects Versions: 2.4.0.Beta1 (Pinto), 2.2.0.SP4, 2.2.1.GA
Reporter: Ron Sigal
Assigned To: Ron Sigal
Fix For: 2.2.2.GA, 2.4.0.Beta1 (Pinto)
If timeout == 0 then
org.jboss.remoting.transport.bisocket.BisocketClientInvoker.createSocket() can hang
forever if the client side is unavailable.
One fix is to not set timeout to 0, but currently the timeout value is inherited from the
server invoker, for which timeout == 0 might be appropriate. One solution is to implement
a separate timeout parameter for callback client invokers (JBREM-765).
Another fix is for PingTimeTask to notify a thread waiting in createSocket() when an
attempt to send a PING to the client fails.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6114
days inactive
6168
days old
6 comments
1 participants
participants (1)
-
Ron Sigal (JIRA)