IBM Support

IT04200: RESTARTING TPC-R WHEN SESSION IS IN "SUSPENDING" STATE RESULTS IN A NULLPOINTEREXCEPTION THAT CAUSES THE SESSION TO NOT DISPLAY

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • Stopping/restarting TPC for Replication when the session is
    Suspending results in a null pointer exception that causes the
    session to
    disappear from TPC-R GUI after restart.
    Evidence of this problem is shown in the csmTraceX.log file
    which corresponds to the time of the restart that resulted in
    this issue, with
    the following messaging:
    2014-08-28 13:47:23.232+0000 CSM.Init RepMgr E e
    com.ibm.csm.server.session.SessionMgr
    restartSessionMgr java.lang.NullPointerException
     at
    com.ibm.csm.server.session.statesmgr.StateMgr.getSessionInfo(Sta
    teMgr.java:1694)
     at
    com.ibm.csm.server.session.statesmgr.StateMgr.hasSuspendedPartic
    ipatingPairs(StateMgr.java:2950)
     at
    com.ibm.csm.server.session.statesmgr.StateMgr.setStatus(StateMgr
    .java:2905)
     at
    com.ibm.csm.server.session.statesmgr.StateMgr.init(StateMgr.java
    :382)
     at
    com.ibm.csm.server.session.statesmgr.StateMgr.<init>(StateMgr.ja
    va:338)
     at
    com.ibm.csm.server.session.SessionMgr.createStateMgrForStartup(S
    essionMgr.java:464)
     at
    com.ibm.csm.server.session.SessionMgr.restartSessionMgr(SessionM
    gr.java:379)
     at
    com.ibm.csm.server.session.SessionMgr.startup(SessionMgr.java:52
    85)
     at com.ibm.csm.server.CSM.initialize(CSM.java:463)
     at com.ibm.csm.server.CSM.access$100(CSM.java:88)
     at com.ibm.csm.server.CSM$CSMInitialize$1.doWork(CSM.java:283)
     at
    com.ibm.csm.server.security.CSMSecurityWrapper$1.run(CSMSecurity
    Wrapper.java:79)
     at
    java.security.AccessController.doPrivileged(AccessController.jav
    a:314)
     at javax.security.auth.Subject.doAs(Subject.java:572)
     at
    com.ibm.csm.server.security.CSMSecurityWrapper.run(CSMSecurityWr
    apper.java:77)
     at com.ibm.csm.server.CSM$CSMInitialize.run(CSM.java:280)
     at java.lang.Thread.run(Thread.java:779)
    The StateMgr.java:1694 message is key - it indicates that the
    infoBuilder is null.
    Not only is the session not visible in the TPC-R GUI, it cannot
    be re-created.  Attempts to re-create the session result in the
    following
    messaging, which indicates that the session already exists:
    IWNR1019E : Session <session_name> was not created because
    another session
    already exists with that name
    RECREATE STEPS:
    1. Get a session to stay in "suspending" state for an indefinite
    amount of time.
    2. Stop TPC-R.
    3. Start TPC-R.
    4. Your session in "suspending" no longer shows up.
    ________________________________________________________________
    DB2 Version used for Server:    N/A
    The defect is against component:   5608TPC00
    Server/Manager build/release (TPC):   5.2.1.0
    
    ________________________________________________________________
    Problem as described by customer:   Phantom (Ghost) session can
    not be removed
    Initial customer impact (low/med/high): high
    

Local fix

  • Database cleanup script may be required from TPC-R
    support/development. Upgrading to TPC-R 5.2.2 will also
    solve this problem.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users who restart TPC-R while a session is in "Suspending"   *
    * State                                                        *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * | fix pack | 5.2.3-TIV-TPC-FP0000 - target 2Q 2014 |         *
    *                                                              *
    *                                                              *
    * http://www-01.ibm.com/support/docview.wss?&uid=swg21320822   *
    *                                                              *
    * The target dates for future fix packs do not represent a     *
    * formal                                                       *
    * commitment by IBM. The dates are subject to change without   *
    * notice.                                                      *
    *                                                              *
    * If a session is in suspending state while TPC-R is restarted *
    * the status setting does not get set properly during the      *
    * startup. This will cause the information for the session to  *
    * be undefined and not allow the UI to properly get            *
    * information for the session from the server component. This  *
    * problem is fixed in TPC-R 5.2.3.                             *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Contact support                                              *
    ****************************************************************
    

Problem conclusion

Temporary fix

  • Contact support
    

Comments

APAR Information

  • APAR number

    IT04200

  • Reported component name

    TPC

  • Reported component ID

    5608TPC00

  • Reported release

    521

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-09-04

  • Closed date

    2014-09-22

  • Last modified date

    2014-09-22

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

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

Fix information

Applicable component levels

  • R520 PSY

       UP

  • R521 PSY

       UP

  • R522 PSN

       UP

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SS5R93","label":"IBM Spectrum Control"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"521","Line of Business":{"code":"LOB26","label":"Storage"}}]

Document Information

Modified date:
22 February 2022