Update link service manager in AWI 21.0.5 throw exception on unix agent
search cancel

Update link service manager in AWI 21.0.5 throw exception on unix agent

book

Article ID: 263115

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

When we click "update link service manager" we see this error on AWI

 

==> WPsrv_log_001_00.txt <==

20230303/120325.306 - U00011688 Service Manager-Query for 'XXXXXLAG01_UNIX' via 'MQ1CP004' will be processed.

 

==> CPsrv_log_004_00.txt <==

20230303/120325.320 - 33     U00045382 Started Service Manager Lookup for process id '    247846' on '10.104.187.70' with port range '8871-8871'.

20230303/120325.388 - 33               Unhandled Exception in thread MQWorker-1 ID=33

20230303/120325.388 - 33     U00045014 Exception 'java.lang.NumberFormatException: "For input string: "    247846""' at 'java.lang.NumberFormatException.forInputString():65'.

20230303/120325.389 - 33     U00003620 Routine 'com.automic.kernel.impl.DefaultExceptionHandler' forces trace because of error.

20230303/120325.391 - 33     U00003450 The TRACE file was opened with the switches '0000000000000000'.

 

==> WPsrv_log_002_00.txt <==

20230303/120325.431 - U00045009 Error during execution of message 'SVC_FND', the following Exception was thrown: 'java.lang.NumberFormatException:For input string: "    247846"' (RunID: '').

 

==> CPsrv_log_004_00.txt <==

20230303/120325.684 - 33     U00003449 Output to the TRACE file is finished.

20230303/120325.685 - 33     U00045014 Exception 'java.lang.NumberFormatException: "For input string: "    247846""' at 'java.lang.NumberFormatException.forInputString():65'.

20230303/120325.686 - 33     U00003620 Routine 'com.automic.kernel.impl.NATDispatcher' forces trace because of error.

20230303/120325.688 - 33     U00003450 The TRACE file was opened with the switches '0000000000000000'.

20230303/120325.979 - 33     U00003449 Output to the TRACE file is finished.

 

Environment

Release : 21.0.5

Resolution

The issue is fixed in 21.0.5.HF1.

There was an internal defect that was fixed by engineering. It is currently not visible in release notes.