IBM Support

PK88995: IN 6.0, SSLC0002E EXCEPTION IS THROWN WHEN STARTING THE APPLICATION SERVER

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When starting the application server, the following exception is
    observed:
    
    SSLChannelDat E   SSLC0002E: The SSL channel cannot be started
    due to the following incorrect settings:
    com.ibm.ssl.clientAuthentication:null
    
    FFDC:
    Exception =
    com.ibm.wsspi.channel.framework.exception.ChannelException
    Source = com.ibm.ws.ssl.channel.impl.SSLChannel
    probeid = 148
    Stack Dump =
    com.ibm.wsspi.channel.framework.exception.ChannelException:
    Invalid property values found:
    com.ibm.ssl.clientAuthentication:null
    
     at
    com.ibm.ws.ssl.channel.impl.SSLChannelData.readProperties(SSLCha
    nnelData
    .java:671)
     at
    com.ibm.ws.ssl.channel.impl.SSLChannel.delayedInit(SSLChannel.ja
    va:259)
    

Local fix

  • no work around
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V6.0.2                               *
    ****************************************************************
    * PROBLEM DESCRIPTION: When the "clientAuthentication"         *
    *                      property is missing in the              *
    *                      security.xml the SSL channel will       *
    *                      fail to start                           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When starting the application server you might see an
    SSLC0002E exception. This is caused by a missing
    "clientAuthentication" property in the security.xml. When the
    SSL Channel tries to start with the property missing it will
    use the default it has that is null and that causes the
    exception mentioned above and not start.
    

Problem conclusion

  • The correct default was added to the code so when the
    "clientAuthentication" property is retrieved it will give a
    default value of "false" instead of null.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 6.0.2.39.  Please refer to the Recommended Updates
    page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK88995

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    60A

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-06-16

  • Closed date

    2009-09-23

  • Last modified date

    2009-09-23

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R60A PSY

       UP

  • R60H PSY

       UP

  • R60I PSY

       UP

  • R60P PSY

       UP

  • R60S PSY

       UP

  • R60W PSY

       UP

  • R60Z PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
10 February 2022