2:18 a.m.
Add a separate timeout parameter for callback clients
-----------------------------------------------------
Key: JBREM-765
URL: http://jira.jboss.com/jira/browse/JBREM-765
Project: JBoss Remoting
Issue Type: Feature Request
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)
Currently, the timeout set for the server filters down to callback client invokers.
However, it would be useful to be able to specify a different timeout value for callback
clients.
Example. In JBossMessaging the server timeout is set to 0. This causes a problem for
bisocket callback client invokers, since they create sockets by sending a message to the
client side and then calling wait(). If timeout == 0 and the client dies, then the thread
in wait() could wait forever.
--
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
12:21 p.m.
New subject: [JBoss JIRA] Updated: (JBREM-765) Add a separate timeout parameter for callback clients
[ http://jira.jboss.com/jira/browse/JBREM-765?page=all ]
Ron Sigal updated JBREM-765:
----------------------------
Fix Version/s: 2.2.1.SP1
2.2.0.SP4_CP02
Affects Version/s: 2.2.1.GA
2.2.0.SP4_CP02
Add a separate timeout parameter for callback clients
-----------------------------------------------------
Key: JBREM-765
URL: http://jira.jboss.com/jira/browse/JBREM-765
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 2.4.0.Beta1 (Pinto), 2.2.1.GA, 2.2.0.SP4_CP02
Reporter: Ron Sigal
Assigned To: Ron Sigal
Fix For: 2.4.0.Beta1 (Pinto), 2.2.0.SP4_CP02, 2.2.1.SP1
Currently, the timeout set for the server filters down to callback client invokers.
However, it would be useful to be able to specify a different timeout value for callback
clients.
Example. In JBossMessaging the server timeout is set to 0. This causes a problem for
bisocket callback client invokers, since they create sockets by sending a message to the
client side and then calling wait(). If timeout == 0 and the client dies, then the thread
in wait() could wait forever.
--
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:23 p.m.
New subject: [JBoss JIRA] Commented: (JBREM-765) Add a separate timeout parameter for callback clients
[ http://jira.jboss.com/jira/browse/JBREM-765?page=comments#action_12371161 ]
Ron Sigal commented on JBREM-765:
---------------------------------
There is a new configuration parameter,
org.jboss.remoting.callback.ServerInvokerCallbackHandler.CALLBACK_TIMEOUT (actual value
"callbackTimeout"), which can be used to set the timeout value for server side
callback clients. For callback clients the value associated with CALLBACK_TIMEOUT
overrides the value associated with org.jboss.remoting.ServerInvoker.TIMEOUT (actual value
"timeout").
There are multiple ways of setting the CALLBACK_TIMEOUT value. In order of descending
priority:
1. it may be put into the metadata map used in the call to
org.jboss.remoting.Client.addListener();
2. it may be placed in the server's InvokerLocator;
3. it may be placed in the configuration map passed to the server Connector's
constructor.
That is, the value in the metadata map overrides the values in the InvokerLocator and
configuration map, and the value in the InvokerLocator overrides the value in the
configuration map.
The feature has been implemented in the remoting_2_2_0_GA branch.
Unit tests: The feature has been tested for the socket and bisocket transports:
org.jboss.test.remoting.callback.timeout.BisocketCallbackTimeoutTestCase
org.jboss.test.remoting.callback.timeout.SocketCallbackTimeoutTestCase
Add a separate timeout parameter for callback clients
-----------------------------------------------------
Key: JBREM-765
URL: http://jira.jboss.com/jira/browse/JBREM-765
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 2.4.0.Beta1 (Pinto), 2.2.1.GA, 2.2.0.SP4_CP02
Reporter: Ron Sigal
Assigned To: Ron Sigal
Fix For: 2.4.0.Beta1 (Pinto), 2.2.0.SP4_CP02, 2.2.1.SP1
Currently, the timeout set for the server filters down to callback client invokers.
However, it would be useful to be able to specify a different timeout value for callback
clients.
Example. In JBossMessaging the server timeout is set to 0. This causes a problem for
bisocket callback client invokers, since they create sockets by sending a message to the
client side and then calling wait(). If timeout == 0 and the client dies, then the thread
in wait() could wait forever.
--
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-765) Add a separate timeout parameter for callback clients
[ http://jira.jboss.com/jira/browse/JBREM-765?page=all ]
Ron Sigal updated JBREM-765:
----------------------------
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.0.SP4_CP02)
Add a separate timeout parameter for callback clients
-----------------------------------------------------
Key: JBREM-765
URL: http://jira.jboss.com/jira/browse/JBREM-765
Project: JBoss Remoting
Issue Type: Feature Request
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
Currently, the timeout set for the server filters down to callback client invokers.
However, it would be useful to be able to specify a different timeout value for callback
clients.
Example. In JBossMessaging the server timeout is set to 0. This causes a problem for
bisocket callback client invokers, since they create sockets by sending a message to the
client side and then calling wait(). If timeout == 0 and the client dies, then the thread
in wait() could wait forever.
--
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-765) Add a separate timeout parameter for callback clients
[ http://jira.jboss.com/jira/browse/JBREM-765?page=all ]
Ron Sigal updated JBREM-765:
----------------------------
Fix Version/s: 2.4.0.Beta1 (Pinto)
(was: 2.4.0.CR1 (Pinto))
Add a separate timeout parameter for callback clients
-----------------------------------------------------
Key: JBREM-765
URL: http://jira.jboss.com/jira/browse/JBREM-765
Project: JBoss Remoting
Issue Type: Feature Request
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
Currently, the timeout set for the server filters down to callback client invokers.
However, it would be useful to be able to specify a different timeout value for callback
clients.
Example. In JBossMessaging the server timeout is set to 0. This causes a problem for
bisocket callback client invokers, since they create sockets by sending a message to the
client side and then calling wait(). If timeout == 0 and the client dies, then the thread
in wait() could wait forever.
--
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:52 p.m.
New subject: [JBoss JIRA] Closed: (JBREM-765) Add a separate timeout parameter for callback clients
[ http://jira.jboss.com/jira/browse/JBREM-765?page=all ]
Ron Sigal closed JBREM-765.
---------------------------
Resolution: Done
The provision of a unit test for the RMI transport will be done under JBREM-799 "Add
a separate timeout parameter for callback clients, part 2".
Add a separate timeout parameter for callback clients
-----------------------------------------------------
Key: JBREM-765
URL: http://jira.jboss.com/jira/browse/JBREM-765
Project: JBoss Remoting
Issue Type: Feature Request
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)
Currently, the timeout set for the server filters down to callback client invokers.
However, it would be useful to be able to specify a different timeout value for callback
clients.
Example. In JBossMessaging the server timeout is set to 0. This causes a problem for
bisocket callback client invokers, since they create sockets by sending a message to the
client side and then calling wait(). If timeout == 0 and the client dies, then the thread
in wait() could wait forever.
--
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
6822
days inactive
6879
days old
5 comments
1 participants
participants (1)
-
Ron Sigal (JIRA)