Global session cache can cause multiple client instances to reuse incorrectly
configured connections.
-----------------------------------------------------------------------------------------------------
Key: GERONIMO-3749
URL: https://issues.apache.org/jira/browse/GERONIMO-3749
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: AsyncHttpClient
Reporter: Rick McGuire
Priority: Minor
The current connection reuse mechanism relies on a single global session class
per process (or really, per class loader that loads the ahc code) to store all
of the i/o sessions indexed by host/port. Since the selection is made based
totally on host and port, it is possible that one ahc client could end up
reusing a connection created by a client with a completely different connection
configuration. Caching should be implemented using a instance-based cache
rather than a single global session cache.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
