IBM Support

IT27774: CLIENT SESSION INGEST TO CONTAINER POOL CAN HANG IN A RUN STATE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Client session ingest to container pool hung.  The run state
    session don't cancel.  The DB Active Log will be pinned and DB2
    can cancel the thread due to NUM_LOG_SPAN.  The session remains
    in a Run State until the dsmserv is restarted.  This is a
    different problem than APAR IT23996
    
    IBM Spectrum Protect Versions Affected: All platforms V7.1.3 and
    above
    
    Customer/L2 Diagnostics:
    
    A Query  Session will show something like:
    387,619  Tcp/Ip  Run       0 S     4.2 K   79.1 M  Node    
    387,620  Tcp/Ip  Run       0 S    37.6 K   41.2 K  Node    
    427,955  Tcp/Ip  Run       0 S       607    2.5 K  Node    
    
    Servermon show data will have the threads in
    pkWaitConditionTracked.  Example:
    
    Thread 549802, Parent 241: psSessionThread, Storage 25574533,
    AllocCnt 1156671 HighWaterAmt 38094948
    tid=140724187473664, ptid=140734802683648, det=1, zomb=0,
    join=0, result=0, sess=387619, procToken=0, sessToken=387619
    lwp=53569
    
    Thread 549804, Parent 549802: SdCQSinkThread, Storage 27003844,
    AllocCnt 1165545 HighWaterAmt 27082113
    tid=140724120450816, ptid=140724187473664, det=1, zomb=0,
    join=0, result=0, sess=0, procToken=0, sessToken=387619
    lwp=53664
    
    The stack conditions are SdWaitCQEmpty(), and the child thread
    is in SdGetNextDataBuffer().
    
    Example:
    Thread abc (Thread 0x... (LWP 53569)):
    #0  0x0000... in pthread_cond_wait@@GLIBC_2.3.2 () from
    /lib64/libpthread.so.0
    #1  0x0000... in pkWaitConditionTracked ...    <----
    #2  0x0000... in SdWaitCQEmpty ...             <----
    #3  0x0000... in SdStore ...
    #4  0x0000... in sdCreate ...
    #5  0x0000... in CreateBitfile ...
    #6  0x0000... in bfCreate ...
    #7  0x0000... in CreateBitfile ...
    #8  0x0000... in SmDoBackInsNormEnhanced ...
    #9  0x0000... in SmNodeSession ...
    #10 0x0000... in HandleNodeSession ...
    #11 0x0000... in DoNodeGeneral ...
    #12 smExecuteSession (infoP=<optimized out>,..
    #13 0x0000... in psSessionThread ...
    #14 0x0000... in StartThread (startInfoP=0x0) at pkthread.c:4016
    #15 0x0000... in start_thread () from /lib64/libpthread.so.0
    #16 0x0000... in clone () from /lib64/libc.so.6
    
    Thread xyz (Thread 0x... (LWP 53664)):
    #0  0x0000... in pthread_cond_wait@@GLIBC_2.3.2 () from
    /lib64/libpthread.so.0
    #1  0x0000... in pkWaitConditionTracked ...    <----
    #3  0x0000... in SdCQSinkThread  ...           <----
    #4  0x0000... in StartThread ...
    #5  0x0000... in start_thread  ...
    #6  0x0000... in clone () from /lib64/libc.so.6
    
    Initial Impact: Low
    Additional Keywords: sessions hang failed cancel high Active Log
    usage
    

Local fix

  • Schedule a time to restart the dsmserv application to remove the
    hung/orphaned sessions.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All IBM Spectrum Protect server users.                       *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See ERROR DESCRIPTION.                                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply fixing level when available. This problem is currently *
    * projected to be fixed in level 8.1.8. Note that this is      *
    * subject to change at the discretion of IBM.                  *
    ****************************************************************
    

Problem conclusion

  • This problem was fixed.
    Affected platforms for reported release:  AIX, Linux, and
    Windows.
    Platforms fixed:  AIX, Linux, and Windows.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT27774

  • Reported component name

    TSM SERVER

  • Reported component ID

    5698ISMSV

  • Reported release

    81L

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-01-15

  • Closed date

    2019-01-27

  • Last modified date

    2019-01-27

  • 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

    TSM SERVER

  • Fixed component ID

    5698ISMSV

Applicable component levels

[{"Line of Business":{"code":"LOB26","label":"Storage"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGSG7","label":"Tivoli Storage Manager"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"81L"}]

Document Information

Modified date:
13 February 2021