SAP agent lost connection and ends with ENDED_LOST status

book

Article ID: 223694

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

The SAP Agent loses the connection to CPs and is notified as ENDED_LOST in the Agent Activity Panel.
The Agent must be restarted to become operational again. A forced trace is generated.
No dump messages in Quarantaine.

In the agent log file, these kind of messages or similar ones can be found:

============================================================================

20210412/203533.592 - U02000126 There is no connection to the Server, message 'EXAKTJQU' cannot be sent.
20210412/203533.594 - U00003620 Routine 'UCEX_R' forces trace because of error.
20210412/203533.603 - U02000048 TRACE file opened with flags '0000000000000001', max.trace: '9', memory trace: '0', search type: 'S', search string: ''.
20210412/203533.638 - U00003449 Output to the TRACE file is finished.
20210412/203533.638 - U02000010 Connection to Server 'DEHEREMAP2016/10.141.14.60:2218' terminated.
20210412/203533.640 - U02000196 Next attempt to create a CP connection in '600' seconds.
20210412/203533.655 - U00003620 Routine 'UCEX_R' forces trace because of error.
20210412/203533.662 - U02000048 TRACE file opened with flags '0000000000000001', max.trace: '9', memory trace: '0', search type: 'S', search string: ''.
20210412/203533.689 - U00003449 Output to the TRACE file is finished.
20210412/203533.689 - U02000041 Shutdown Agent 'PEU'.
20210412/203533.732 - U02000001 Agent 'PEU' version '12.3.4+build.1601882670514' ended normally.
20210412/203533.732 - U02000126 There is no connection to the Server, message 'EXSTOP' cannot be sent.

============================================================================

The forced trace thrown by this agent may contain:

============================================================================

20210412/203316.329 - 1   java.io.IOException: An existing connection was forcibly closed by the remote host
        at java.base/sun.nio.ch.SocketDispatcher.write0(Native Method)
        at java.base/sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:51)
        at java.base/sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:113)
        at java.base/sun.nio.ch.IOUtil.write(IOUtil.java:79)
        at java.base/sun.nio.ch.IOUtil.write(IOUtil.java:50)
        at java.base/sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:463)
        at com.uc4.ex.cp.CPConnection.sendBuffer(CPConnection.java:853)
        at com.uc4.ex.cp.CPConnection.send(CPConnection.java:683)
        at com.uc4.ex.JobRoutine.sendAllJobStates(JobRoutine.java:911)
        at com.uc4.ex.ExecutorLifecycle.checkJobStatusTimer(ExecutorLifecycle.java:251)
        at com.uc4.ex.ExecutorLifecycle.execute(ExecutorLifecycle.java:140)
        at com.uc4.ex.sap.UCXJR3X.main(UCXJR3X.java:69)

============================================================================

Communication Process may log the following messages:

============================================================================

20210412/203316.456 - U00003412 Agent 'PEU' logged on (Client connection='338').
20210412/203316.456 - U01002200 Received an invalid message from partner 'PEU' via connection '10.141.14.61:56064'.
20210412/203316.456 - U01002203 Field 'Protocol' in message header is invalid.
20210412/203316.456 - U00009907 Memory dump 'Invalid Msg from Agent PEU' (Address='0000000009EEF040', Length='1386')

============================================================================

Cause

This is a bug of the SAP Agents. 

 

Environment

Release : 12.3 Component : AUTOMATION ENGINE

 

Resolution

A problem has been fixed where the Agent, after losing the CP connection, reconnected without initializing GSS, sent an unencoded EXSTART2 message, and was notified as ENDED_LOST.

Workaround:

Restart the impacted agent.

Solution:

Update to a fix version listed below or a newer version if available.

Automation.Engine 12.3.7  - Planned release in November 2021
Automation.Engine 21.0.0  - Planned release in October 2021

Additional Information

Following agents may be also affected by this problem : SQL Agent, Peoplesoft Agent,JMX Agent,SAP Agent, RA Core Agent