DO NOT REPLY [Bug 11305] - Client of stateful service connects to incorrect service instance

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11305>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11305

Client of stateful service connects to incorrect service instance

gdaniels@macromedia.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED



------- Additional Comments From gdaniels@macromedia.com  2002-08-06 12:46 -------
Thanks, Alan!

This brought to light a serious problem in the Call object.  We were caching 
Transport objects (which is where the session cookies get stored) on a per-
address basis in a static Hashtable.  As such, when multiple threads talked to 
the same address, they ended up sharing Transports - which is not really the 
logical behaviour.  In some cases, you want this so that different 
services/clients can share a concept of "connection", but I think we need to 
architect it much more intelligently and flexibly if we want that 
functionality.  For now, I made the cache non-static, and your test works fine.

Thanks!