[
http://jira.jboss.com/jira/browse/JBREM-986?page=comments#action_12414510 ]
Ron Sigal commented on JBREM-986:
---------------------------------
Updated MicroSocketClientInvoker. Also, updated org.jboss.remoting.ConnectionValidator,
which used to set a "numberOfRetries" value for the socket transport.
Unit test: org.jboss.test.remoting.connection.ConnectionWaitTestCase.
Waiting for hudson results.
Make configurable time MicroSocketClientInvoker should wait to get
connection from pool
---------------------------------------------------------------------------------------
Key: JBREM-986
URL:
http://jira.jboss.com/jira/browse/JBREM-986
Project: JBoss Remoting
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Ron Sigal
Assigned To: Ron Sigal
Fix For: 2.4.0.GA (Pinto)
1. org.jboss.remoting.transport.socket.MicroSocketClientInvoker.getConnection() waits to
get a semaphore, which gives it permission to try to obtain a network connection.
Currently, the maximum wait time is hard coded to be 30000 ms. This value should be
configurable.
2. The use of semaphores replaces older code that looped, trying to obtain a connection.
The number of attempts was governed by the parameter "numbofOfRetries". This
parameter should be eliminated.
--
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