FS6200 Server System Implementation Guide - Public Support ...

Restarting a JProcessor Specialty Engine
Periodically, the JProcessor Specialty Engine firmware sends a heartbeat message to the
MCPJava support library. When the MCPJava support library does not receive the
heartbeat message, it reports that the JProcessor Specialty Engine is not responding by
initiating a waiting RSVP task named JAVASUPPORT/SERVER/n/NOT/RESPONDING. This
task displays the following message at the ODT.
Java Monitor is not responding for Java server n,
check the Java server or AX to terminate this task and wait for an AX or DS
In the preceding message, the variable n is the number of the JProcessor Specialty
Engine.
Use the NA JAVA SERVER command to determine if the server state as “Unavailable”.
Perform the following steps to restart a JProcessor Specialty Engine:
Note: The command examples in this procedure assume you have set up your
JProcessor Specialty Engines in a server pool.
1. Check the TCPIP connection to the JProcessor Specialty Engine using the following
commands:
• JProcessor Specialty Engine 1
NW CONN 2101_TCPIP_2101
• JProcessor Specialty Engine 2
NW CONN 2201_TCPIP_2201
• JProcessor Specialty Engine 3
NW CONN 2102_TCPIP_2102
• JProcessor Specialty Engine 4
NW CONN 2202_TCPIP_2202
The response should indicate the CONNECTIONSTATUS = OPEN.
2. If the connection status is not OPEN, establish the connection using the following
commands:
NW ESTABLISHCALL BY CONN 2101_TCPIP_2101
NW EC BY CONN 2201_TCPIP_2201
NW ESTABLISHCALL BY CONN 2102_TCPIP_2102
NW EC BY CONN 2202_TCPIP_2202
3. If necessary, clear the connection using the following command:
NW CLEARCALL 2101_TCPIP_2101
NW CC 2201_TCPIP_2201
NW CLEARCALL 2102_TCPIP_2102
NW CC 2202_TCPIP_2202
Troubleshooting and Recovery
8222 3694–000 9–17