SESSION_ERROR: Connection refused
search cancel

SESSION_ERROR: Connection refused

book

Article ID: 421336

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

While running a job, we see the following when stopping/starting the agent:

-1 - Wrong message type
20251114/200926.271 U0009909 TRACE: (wrong type error)              0x1e3f3d0 01268
                    00000000  53455353 494F4E5F 4552524F 52000000  >SESSION_ERROR...<
                    00000010  00000000 00000000 00000000 00000000  >................<
                    00000020  2A414745 4E540000 00000000 00000000  >*AGENT..........<
                    00000030= 00000000 00000000 00000000 00000000  >................<
                    00000060  00000000 00000000 756E6B6E 6F776E00  >........unknown.<
                    00000070= 00000000 00000000 00000000 00000000  >................<
                    000000F0  B9851E00 2A414745 4E547C6F 6E5F636F  >....*AGENT|on_co<
                    00000100  6E6E6563 74696F6E 2F313131 28436F6E  >nnection/111(Con<
                    00000110  6E656374 696F6E20 72656675 73656429  >nection refused)<
                    00000120= 00000000 00000000 00000000 00000000  >................<
                    000004F0  00000000                             >....<

 

Environment

Automic Automation Engine

Cause

There were multiple JCPs defined in the agent's ucxjlx6.ini. When commenting out the other JCP's, the issue did not appear.

Resolution

First, make sure that the port is defined as described here: Wrong message type - SESSION_ERROR in Job Report

Next, make sure that the agent has the certificates for each of the JCP's in the folder defined by the trustedCertFolder property - located in the agent's ucxjlx6.ini.