[jboss-jira] [JBoss JIRA] Commented: (JBREM-765) Add a separate timeout parameter for callback clients
Ron Sigal (JIRA)
jira-events at lists.jboss.org
Sun Aug 5 16:23:49 EDT 2007
[ 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
More information about the jboss-jira
mailing list