[
http://jira.jboss.com/jira/browse/JBREM-701?page=all ]
Ron Sigal updated JBREM-701:
----------------------------
Fix Version/s: 2.2.0.Beta2 (Bluto)
(was: 3.0.0.Alpha1 (Otter))
Affects Version/s: 2.2.0.Beta2 (Bluto)
(was: 3.0.0.Alpha1 (Otter))
For the http and rmi transports, the solution is to run the invocation in another thread
and wait until the timeout expires.
add timeout config per client invocation for transports not descended
from socket transport
-------------------------------------------------------------------------------------------
Key: JBREM-701
URL:
http://jira.jboss.com/jira/browse/JBREM-701
Project: JBoss Remoting
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 2.2.0.Beta2 (Bluto)
Reporter: Ron Sigal
Assigned To: Ron Sigal
Fix For: 2.2.0.Beta2 (Bluto)
For JBREM-598 per invocation timeouts were implemented for socket, sslsocket, bisocket,
and sslbisocket. It's not clear how to implement per invocation timeouts for http and
rmi, but it would be good to do, if possible.
--
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