Agent-Advisor connection terminates unexpectedly

Check the following:
  • Verify that the Agent's MVS™ operator has not shut down the Agent.
  • Verify that TCP/IP connectivity still exists between the Agent and the Advisor.
  • Check the Advisor's log file for ERROR or WARNING messages and take the appropriate corrective action. If you see an ERROR message indicating a send() operation failed with errno = EDC8102I Operation would block, you might have too many groups or members registered that belong to the same Agent. Increase the TCPSENDBFRSIZE parameter of the TCPCONFIG PROFILE.TCPIP statement, or register fewer groups and members belonging to the Agent. Then try the operation again.
    Tip: Keep in mind that the Advisor and Agent have an internal maximum message size of 128KB. If this limit is exceeded, the connection is closed and an error message is logged, which states that the message is too big and was not received.

    If ERROR and WARNING level log messages are not enabled, enable them, repeat the operation, and recheck the log file again.

  • Check the Agent's log for errors.
  • Connectivity can be dropped between the Advisor and Agents if processing slows down too much (due to lots of registered members and/or high debug levels) and the update_interval is configured too low. Using AT-TLS could increase the possibility of this happening. Try increasing the update_interval.
Parent topic: Diagnosing Advisor and Agent problems