IBM Support

PI14045: UN-REGISTERING DEPLOYMENT MANAGER FROM JOB MANAGER CAUSES TRUST.P12 TO BECOME AN EMPTY FILE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When a user un-registers a deployment manager (dmgr) from a job
    manager, and the job manager and dmgr are the same JVM,
    it can cause the trust.p12 file of the dmgr to become an empty
    file. The next start of the dmgr might then fail as follows:
    
    java.io.IOException: Keystore file exists, but is empty:
    /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/config/cells/Cell01
    /trust.p12
    ....
    

Local fix

  • After de-registering, the dmgr profile can be recovered by
    simply by copying the trust.p12 file in the profile directory:
    
    cp -p /etc/trust.p12
    /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/config/cells/
    Cell01/trust.p12
    
    Then the dmgr will start up without error.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V8.0 and V8.5                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: Unregistering a deployment manager      *
    *                      from a job manager can introduce a      *
    *                      dmgr startup failure.                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Unregistering a dmgr from a jobmgr can introduce a dmgr
    startup failure when the two entities are in the same JVM.
    

Problem conclusion

  • Part of deregistering is to remove the certificates of the
    dmgr from the job manager, since it is assumed they will
    no longer need to be communicating with each other.  However,
    when these two entities are the same JVM, this can result in
    an empty truststore, which prevents server startup if security
    is enabled.
    
    The code is revised to detect when a dmgr is deregistering
    from itself, and not remove the certificates in that case.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 8.0.0.10 and 8.5.5.3.  Please refer to the
    
    Recommended Updates page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

  • There is usually a copy of the trust.p12 file in the
    (profile_root)/etc directory.  It can be copied over
    the damaged file, then the dmgr. will start.
    

Comments

APAR Information

  • APAR number

    PI14045

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-03-19

  • Closed date

    2014-04-09

  • Last modified date

    2015-01-15

  • 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

  • R800 PSY

       UP

  • R850 PSY

       UP

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

Document Information

Modified date:
28 April 2022