IBM Support

JR43911: ASB Agent Startup exhausts sessions if the Agent port is already in use.

 

APAR status

  • Closed as fixed if next.

Error description

  • When agent was re-started while it was still running and
    listening on port 31531 then the sessions are exhausted.
    
    NodeAgents.sh invokes Agent.sh.  Agent.sh has retry logic in it
    for runtime, to re-start the agent in the event that it exits.
    In this case, when Agent.sh started the agent, the agent began
    its initialization process, but when it tried to listen on port
    31531, it failed and exited.  Agent.sh then tried to start the
    agent again and this was continuously repeated.
    
    Part of the agent initialization process is to invoke attached
    handlers so that they can perform their own initialization.  In
    this case, the IA handler authenticated, but was never given a
    chance to shutdown. After enough repeated attempts at starting
    the agent and invoking the IA handler without proper shutdown,
    sessions were exhausted.
    
    Another possible symptom of this issue is excessive CPU usage by
    the agent process due to continous retrying.  The actual process
    ID will vary as a new agent process is started when the errant
    one exits.
    

Local fix

  • Make sure agents are shutdown properly.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users that have IA installed and restart the ASB Agent while the
    port is in use.
    ****************************************************************
    PROBLEM DESCRIPTION:
    When the ASB Agent is started while its port is in use, its
    initialization fails and an ISF session is leaked from the IA
    handler.  Agent.sh continuously attempts to restart the ASB
    Agent and eventually all ISF sessions get used up.
    ****************************************************************
    RECOMMENDATION:
    After stopping the agents, or prior to starting the agents,
    execute the following to check for the ASB Agent process running
    and/or the ASB Agent port in use:
    
    ps -ef | grep AgentImpl
    
    netstat -an | grep 31531
    
    The default ASB Agent port is 31531.  If a different port was
    chosen during install, substitute the actual port value for
    31531.
    
    ****************************************************************
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    JR43911

  • Reported component name

    WIS INFORM ANAL

  • Reported component ID

    5724Q36IA

  • Reported release

    850

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-08-28

  • Closed date

    2012-11-28

  • Last modified date

    2013-12-18

  • 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

  • R870 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSZJLG","label":"InfoSphere Information Analyzer"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5"}]

Document Information

Modified date:
12 October 2021