IBM Support

PM00163: A SERVER WON'T START IF THERE ARE INCONSISTENCIES IN SECURITY.XML

Fixes are available

7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for IBM i
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Windows
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for AIX
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for HP-UX
7.0.0.9: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Solaris
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Linux
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for IBM i
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Windows
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for HP-UX
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for AIX
7.0.0.11: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Solaris
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If there are some inconsitencies in attributes of
    sslConfigGroups tag, a server will not start with the following
    exception:
    
    [10/28/09 10:48:45:504 CET] 00000000 WsServerImpl  E   WSVR010
    0W: An error occurred initializing, dmgr [class com.ibm.ws.run
    time.component.ServerImpl]
    com.ibm.ws.exception.ConfigurationError: com.ibm.websphere.ssl
    .SSLException: java.lang.NullPointerException
    at com.ibm.ws.ssl.core.SSLComponentImpl.initialize(SSLComponen
    tImpl.java:208)
    at com.ibm.ws.runtime.component.ContainerHelper.initWsComponen
    t(ContainerHelper.java:1191)
    at com.ibm.ws.runtime.component.ContainerHelper.initializeComp
    onent(ContainerHelper.java:1098)
    at com.ibm.ws.runtime.component.ContainerHelper.initializeComp
    onents(ContainerHelper.java:900)
    at com.ibm.ws.runtime.component.ContainerImpl.initializeCompon
    ents(ContainerImpl.java:776)
    at com.ibm.ws.runtime.component.ContainerImpl.initializeCompon
    ents(ContainerImpl.java:750)
    at com.ibm.ws.runtime.component.ServerImpl.initialize(ServerIm
    pl.java:333)
    at com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServe
    rImpl.java:280)
    at com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl.java:214)
    at com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl.java:666)
    at com.ibm.ws.runtime.WsServer.main(WsServer.java:59)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcc
    essorImpl.java:48)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingM
    thodAccessorImpl.java:37)
    at java.lang.reflect.Method.invoke(Method.java:600)
    at com.ibm.wsspi.bootstrap.WSLauncher.launchMain(WSLauncher.ja
    va:213)
    at com.ibm.wsspi.bootstrap.WSLauncher.main(WSLauncher.java:93)
    at com.ibm.wsspi.bootstrap.WSLauncher.run(WSLauncher.java:74)
    at org.eclipse.core.internal.runtime.PlatformActivator$1.run(P
    latformActivator.java:78)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLaunche
    r.runApplication(EclipseAppLauncher.java:92)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLaunche
    r.start(EclipseAppLauncher.java:68)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(Eclipse
    Starter.java:400)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(Eclipse
    Starter.java:177)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcc
    essorImpl.java:48)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingM
    ethodAccessorImpl.java:37)
    at java.lang.reflect.Method.invoke(Method.java:600)
    at org.eclipse.core.launcher.Main.invokeFramework(Main.java:34
    0)
    at org.eclipse.core.launcher.Main.basicRun(Main.java:282)
    at org.eclipse.core.launcher.Main.run(Main.java:981)
    at com.ibm.wsspi.bootstrap.WSPreLauncher.launchEclipse(WSPreLa
    uncher.java:340)
    at com.ibm.wsspi.bootstrap.WSPreLauncher.main(WSPreLauncher.ja
    va:110)
    Caused by: com.ibm.websphere.ssl.SSLException: java.lang.NullP
    ointerException
    at com.ibm.ws.ssl.config.SSLConfigManager.initializeServerSSL(
    SSLConfigManager.java:331)
    at com.ibm.ws.ssl.core.SSLComponentImpl.initialize(SSLComponen
    tImpl.java:145)
    ... 31 more
    Caused by: java.lang.NullPointerException
    at com.ibm.ws.ssl.config.ManagementScopeManager.loadSSLConfigG
    roups(ManagementScopeManager.java:546)
    at com.ibm.ws.ssl.config.SSLConfigManager.initializeServerSSL(
    SSLConfigManager.java:326)
    ... 32 more
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: WebSphere Application Server doesn't    *
    *                      start when security.xml contains        *
    *                      incorrect entry.                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    WebSphere Application Server doesn't start up when
    security.xml contains an entry which the security code doesn't
    recognize. The following is one of examples:
    <sslConfigGroups xmi:id="SSLConfigGroup_1250772929209"
    name="fmtc5223WPSNode01" direction="inbound">
    <sslConfig
    href="security.xml#SSLConfig_fmtc5223WPSNode01_1"/>
    <managementScope
    href="security.xml#ManagementScope_fmtc5223WPSNode01_1"/>
    </sslConfigGroups>
    
    The cause of the error is that one of methods in
    loadSSLConfigGroups.class doesn't check whether
    an object is valid before accessing it.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PM00163

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-10-30

  • Closed date

    2009-11-09

  • Last modified date

    2009-11-09

  • 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

    WEBSPHERE APP S

  • Fixed component ID

    5724J0800

Applicable component levels

  • R700 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 October 2021