IBM Support

IC37911: ANR9999D PKTHREAD.C(636): THREADID<13> THREAD CREATION FAILED: RC=11,4.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • ANR9999D pkthread.c(636): ThreadId<13> Thread creation
    failed; rc=11,4.
    ANR0485W Session 151 for node DUNAEVSKIY (Linux86)
                             terminated - sufficient memory is not a
    no entries in /var/log/messages
    The return codes on the pthread_create() function call translate
    to
    #define EINTR            4      /* Interrupted system call */
    #define EAGAIN          11      /* Try again */
    .
    Problem is reported with parallel sessions (customer created
    with 10 parallel sessions, inhouse recreation was possible
    with up to 80 parallel sessions)
    .
    

Local fix

  • Apply fix once available
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of TSM Server for Linux,           *
    *                 versions 5.1 and above.                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: When multiple clients connect           *
    *                      simultaneously to the TSM server,       *
    *                      and these clients are running heavy     *
    *                      backup sessions, the TSM Server reaches *
    *                      a point where it cannot create threads  *
    *                      necessary to handle all of the client   *
    *                      sessions.                               *
    ****************************************************************
    * RECOMMENDATION: Apply fixing patch when available. This      *
    *                 problem is currently projected to be fixed   *
    *                 in patch 5.2.1.3, PTF 5.1.9 and PTF 5.2.2.   *
    *                 Note that this is subject to change at the   *
    *                 discretion of IBM.                           *
    ****************************************************************
    When multiple clients connect simultaneously to the TSM
    server, and these clients are running heavy backup sessions,
    the TSM Server reaches a point where it cannot create
    threads necessary to handle all of the client sessions.
    

Problem conclusion

  • TSM Server can now accept multiple
    simultaneous client ceonnections, with each connection
    running heavy backup/restore sessions, and without running
    out of resources to create the threads required by each session.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC37911

  • Reported component name

    TSM SERVER 510

  • Reported component ID

    5698ISMSV

  • Reported release

    52L

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2003-10-24

  • Closed date

    2003-10-30

  • Last modified date

    2003-10-30

  • 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 510

  • Fixed component ID

    5698ISMSV

Applicable component levels

  • R51L PSY

       UP

  • R52L PSY

       UP

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

Document Information

Modified date:
30 October 2003