axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Davanum Srinivas (JIRA)" <axis-...@ws.apache.org>
Subject [jira] Resolved: (AXIS-1562) SocketFactoryFactory & HTTPSender limit to one socket factory per protocol
Date Tue, 14 Dec 2004 13:33:07 GMT
     [ http://nagoya.apache.org/jira/browse/AXIS-1562?page=history ]
     
Davanum Srinivas resolved AXIS-1562:
------------------------------------

    Resolution: Fixed

Closing bug as per clive's remarks.

thanks,
dims

> SocketFactoryFactory & HTTPSender limit to one socket factory per protocol
> --------------------------------------------------------------------------
>
>          Key: AXIS-1562
>          URL: http://nagoya.apache.org/jira/browse/AXIS-1562
>      Project: Axis
>         Type: Bug
>   Components: Basic Architecture
>     Versions: 1.2 Beta
>  Environment: All
>     Reporter: Clive Brettingham-Moore
>     Priority: Minor

>
> org.apahce.axis.components.net.SocketFactoryFactory has a static method used to get a
socket factory, with parameters for the protocol and a set of options. The method caches using
a static hashtable with protocol as key; as a concequence axis can only support one SocketFactory
per protocol. Since for HTTPS certificate configuration is carried out via the SocketFactory
this is a problem for enterprise apps that must use multiple SSL web services concurrently
(or even non-concurrently).
> I have submitted this as a bug since it is a deficiency in a core function of the library,
and is in stark contrast to the flexability of almost every other axis feature.
> (There are work arounds, thanks to the configurability mentioned, such as a custom context-aware
SocketFactory, but there are still issues with running multiple applications in the same classloader
scope wrt axis)
> there are many solutions to this issue, some sort of finer factory configuration is needed,
eg instance based configuration, or ContextClassLoader keyed static config; simple static
management is not workable in enterprise applications.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Mime
View raw message