IBM Support

JR35568: AGENT SEEMS HUNG, APPLICATION REPORTS "AGENT NOT AVAILABLE"

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • agent process seems to be running fine, however applications
    cannot connect. return message "agent not available"
    

Local fix

  • *  Add the following lines to the Agent.sh prior to the
    point where RunAgent is called.  The changes would look like
    this (bold lines are the new lines):
    
    AIXTHREAD_SCOPE=S
    export AIXTHREAD_SCOPE
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    ISD users on AIX.
    ****************************************************************
    PROBLEM DESCRIPTION:
    The ASBAgent can become unresponsive for no apparent reason.
    Requests will usually recieve an error such as "No Agents are
    available to handle the request." even though the ASBAgent
    process is running. Executing the command "netstat -an | grep
    31531" on the computer where the ASBAgent is running will show
    a number of sockets in a CLOSE_WAIT state.
    ****************************************************************
    RECOMMENDATION:
    Install 8.1 Rollup Patch 1.
    ****************************************************************
    

Problem conclusion

  • On AIX, the ASBAgent process uses an application called
    RunAgent to wrap the java code. In doing so it does not ensure
    that the AIXTHREAD_SCOPE environment variable is set to the
    value "S". Without this setting, low level threads can become
    deadlocked and cause the ASBAgent process to become
    unresponsive.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR35568

  • Reported component name

    WIS DATASTAGE

  • Reported component ID

    5724Q36DS

  • Reported release

    810

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-02-04

  • Closed date

    2010-03-10

  • Last modified date

    2010-03-10

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

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

Modules/Macros

  • SERVER
    

Fix information

  • Fixed component name

    WIS DATASTAGE

  • Fixed component ID

    5724Q36DS

Applicable component levels

  • R810 PSN

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSVSEF","label":"IBM InfoSphere DataStage"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
10 March 2010