IBM Support

PI91977: WebSphere Application Server config files length zero bytes

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • Closed as program error.

Error description

  • WebSphere configuration files like security.xml or server.xml
    are found to be zero bytes.
    Nothing appears to monitor or detect zero length XML files in
    the repository.
    This causes major issues trying to run WebSphere.
    An example of what happens when the security.xml file is zero
    bytes and WebSphere is set to run as a Windows service:
    --------
    instance is not accessible - Service crash after a few minutes.
    see the following in WAS systemout:
    [27.11.17 07:46:38:639 CET] 00000001 SSLComponentI I
    CWPKI0001I: SSL service is initializing the configuration
    [27.11.17 07:46:38:749 CET] 00000001 FfdcProvider W
    com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC
    Incident emitted on
    D:\IBM\WebSphere\AppServer\profiles\AppSrv01\logs\ffdc\
    server1_b9699d77_17.11.27_07.46.38.6557402039700432314128.txt
    com.ibm.ws.ssl.core.SSLComponentImpl.initialize 200
    [27.11.17 07:46:38:749 CET] 00000001 SSLComponentI A
    CWPKI0007I: SSL service failed to start successfully
    [27.11.17 07:46:38:749 CET] 00000001 WsServerImpl E WSVR0100W:
    An error occurred initializing, server1 [class
    com.ibm.ws.runtime.component.ServerImpl]
    com.ibm.ws.exception.ConfigurationError:
    com.ibm.websphere.ssl.SSLException:
    Cannot get security object from WCCM.
    at
    com.ibm.ws.ssl.core.SSLComponentImpl.initialize(SSLComponentImpl
    .java:208)
    at
    com.ibm.ws.runtime.component.ContainerHelper.initWsComponent(Con
    tainerHelper.java:1193)
    --------
    There is some correlation to the security.xml file getting
    corrupted to zero bytes and the scheduled job to check /
    monitor the expiration dates of the SSL certificates.
    

Local fix

  • To be prepared in case the security.xml file gets set to zero
    bytes, make sure your back up processes back up security.xml
    file and make sure the backup of the security.xml file is not
    zero bytes, so that if you need to recover it you will have a
    valid file.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: Server fails to start because           *
    *                      security.xml is empty.                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    In rare circumstances the security.xml file may be truncated to
    0 length which causes the server to fail to start.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PI91977

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-01-02

  • Closed date

    2018-02-05

  • Last modified date

    2018-02-05

  • 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



Document information

More support for: WebSphere Application Server
General

Software version: 850

Reference #: PI91977

Modified date: 05 February 2018


Translate this page: