river-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bob Scheifler (JIRA)" <j...@apache.org>
Subject [jira] Created: (RIVER-31) HttpsEndpoint.EndpointInfo.connect should not establishCallContext while synchronized
Date Wed, 27 Jun 2007 18:49:26 GMT
HttpsEndpoint.EndpointInfo.connect should not establishCallContext while synchronized
-------------------------------------------------------------------------------------

                 Key: RIVER-31
                 URL: https://issues.apache.org/jira/browse/RIVER-31
             Project: River
          Issue Type: Bug
            Reporter: Bob Scheifler


In HttpsEndpoint.EndpointInfo.connect, if an existing connection can't be reused, a new HttpsConnection
is created and establishCallContext is called on it.  Both of the latter are done while still
holding the EndpointInfo lock, and establishCallContext does connection establishment and
SSL handshake, which can take a long time. As a result, concurrent calls are unable to proceed
concurrently.  I believe these can and should be pulled out of the synchronized block (similar
to ConnectionManager.connect).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message