servicemix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guillaume Nodet (JIRA)" <>
Subject [jira] Resolved: (SM-426) ProviderProcessor https connection fails
Date Fri, 05 May 2006 23:59:43 GMT
     [ ]
Guillaume Nodet resolved SM-426:

    Fix Version: 3.0-M2
     Resolution: Fixed
      Assign To: Guillaume Nodet

Author: gnodet
Date: Fri May  5 16:58:15 2006
New Revision: 400214

SM-411 et SM-426: fix servicemix-http client side ssl support


> ProviderProcessor https connection fails
> ----------------------------------------
>          Key: SM-426
>          URL:
>      Project: ServiceMix
>         Type: Bug

>   Components: servicemix-http
>     Versions: 3.0
>  Environment: Windows XP
>     Reporter: Kevin Bouchard
>     Assignee: Guillaume Nodet
>      Fix For: 3.0-M2

> Original Estimate: 1 minute
>         Remaining: 1 minute
> The trustStorePassword is not set correctly at service assembly startup, precisely when
the CommonsHttpSSLSocketFactory is created. This issue cause a NullPointerException to be
thrown when the trustStore location is not set in the classpath of the application.
> Once this problem is fixed, the connection still fails. The reason is that the CommonsHttpSSLSocketFactory
is not called when the socket is to be created. The DefaultSSLSocketFactory is called instead
since Protocol.registerProtocol("https",protocol) function is missing at service assembly
startup. This cause a SocketException to be thrown with reason "password can't be null".

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message