You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Jeremy Boynes (JIRA)" <de...@geronimo.apache.org> on 2005/09/17 05:17:54 UTC

[jira] Commented: (GERONIMO-1011) HTTPS Connectors fail on IBM JDK

    [ http://issues.apache.org/jira/browse/GERONIMO-1011?page=comments#action_12329604 ] 

Jeremy Boynes commented on GERONIMO-1011:
-----------------------------------------

Fixed in a slightly different way
Sending        modules/assembly/src/plan/j2ee-jetty-plan.xml
Sending        modules/assembly/src/plan/j2ee-tomcat-plan.xml
Sending        modules/jetty/src/java/org/apache/geronimo/jetty/connector/HTTPSConnector.java
Sending        modules/tomcat/src/java/org/apache/geronimo/tomcat/HttpsConnectorGBean.java
Transmitting file data ....
Committed revision 289691.

This change allows the user to specify a value of "Default" for the algorithm which causes the connector to obtain the platform default from the KeyManagerFactory. This is standard Java and should work on any JVM.

This does not affect the client-side behaviour.

> HTTPS Connectors fail on IBM JDK
> --------------------------------
>
>          Key: GERONIMO-1011
>          URL: http://issues.apache.org/jira/browse/GERONIMO-1011
>      Project: Geronimo
>         Type: Bug
>   Components: JVM-compatibility
>     Versions: 1.0-M5
>  Environment: WinXP or Win2003 Server w/ IBM 1.4.2 JDK
>     Reporter: Donald Woods
>  Attachments: IBMJUnit.patch, IBMSSL.patch
>
> HTTPS connectors for Jetty and Tomcat fail to load when starting the server using the IBM 1.4.2 JDK.
> This worked with M4, but was broken sometime in the last several weeks by changes in M5.
> The IBM JDK supplies its own HTTPS handler - com.ibm.net.ssl.www.protocol, which must be manually loaded in addition to the default sun.net.www.protocol.
> Also, the IBM JDK provides a different implementation of the X059 algorithm, which is IbmX509 instead of SunX509.
> The required code changes to recognize that an IBM JDK is being used and initialize the algorithm and protocol handler correctly, are confined to the Jetty and Tomcat HttpsConnector classes and the GeronimoURLFactory.
> The resolution of this bug will only allow a Geronimo server built with the Sun JDK to run on an IBM JDK - it does not resolve the other known build and Orb problems with using non-Sun JVMs.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira