IBM Support

Unexpected agent/integration server down

Troubleshooting


Problem

This issue was seen when there were multiple agent/integration server boxes. Multiple instances of common agent/integration servers are run in these boxes. Consider a scenario where agent server 1 is being run in agent server box 1 and agent server box 2 When agent server 1 is being stopped in agent server box 1, the server stops in agent server box 2 as well and does not come back until they are started from agent server box 2.

Symptom

The server with common server name running on a different box went down unexpectedly.

Cause

This is due to running stopIntegrationServer.sh <server name>

Diagnosing The Problem

If you run 'stopIntegrationServer; without any command, the following is the usage hint.
Usage:
-id <Server ID>
-name <Server Name>

If you provide Server Name, all associated Server ID's of that Server will be shut down.
It does not matter from which box this command is run, it will stop the servers based on the server ID or server name supplied. If name is supplied all servers will be stopped. if ID is supplied then only the
specific server with that ID will be stopped.

Resolving The Problem

Run 'stopIntegrationServer -id <Server ID>. Server ID is printed during the server startup.

[{"Product":{"code":"SS6PEW","label":"Sterling Order Management"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Documentation","Platform":[{"code":"PF016","label":"Linux"}],"Version":"9.5","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
16 June 2018

UID

swg22006458