Fix serious bug - we were, for some reason, caching Transports in a static Hashtable, so multiple threads using the Call object would end up sharing them, therefore stomping on each other's transport-specific information!
Fix serious bug - we were, for some reason, caching Transports in a
static Hashtable, so multiple threads using the Call object would end up
sharing them, therefore stomping on each other's transport-specific
information!

In fact, sharing transports should be controllable - sometimes even for
the same address you don't want this!  But this fixes a bug for now:

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

Thanks to Alan Moore for the bug report!

TODO : Add multi-threaded session test, which would have caught
this.


git-svn-id: 8699849808240b02471d01f5aaa03ec0c1cb68ee@247660 13f79535-47bb-0310-9956-ffa450edef68

apache/axis1-java,apache/axis1-java,apache/axis1-java,apache/axis1-java