U00003422 WARNING: Cannot load conversation memory causes floods the WP logs

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

Following an upgrade to 21.0.9 (Including HF1 and HF2), the WP are flooded with messages

WPsrv_log_006_00

20240313/113351.005 - U00003422 WARNING: Cannot load conversation memory '0ce331c5' for server routine 'UCGENX_R'.
20240313/113351.021 - U00003422 WARNING: Cannot load conversation memory '0ce331c5' for server routine 'UCGENX_R'.
20240313/113351.021 - U00003422 WARNING: Cannot load conversation memory '0ce32a11' for server routine 'UCGENX_R'.
20240313/113351.036 - U00003422 WARNING: Cannot load conversation memory '0ce32a11' for server routine 'UCGENX_R'.
20240313/113353.085 - U00003422 WARNING: Cannot load conversation memory '0ce331c5' for server routine 'UCGENX_R'.
20240313/113353.617 - U00003422 WARNING: Cannot load conversation memory '0ce32a11' for server routine 'UCGENX_R'.
20240313/114503.106 - U00003422 WARNING: Cannot load conversation memory '0ce32a1b' for server routine 'UCGENX_R'.
20240313/114503.106 - U00003422 WARNING: Cannot load conversation memory '0ce32a1b' for server routine 'UCGENX_R'.
20240313/114503.106 - U00003422 WARNING: Cannot load conversation memory '0ce32a34' for server routine 'UCGENX_R'.
20240313/114503.122 - U00003422 WARNING: Cannot load conversation memory '0ce32a34' for server routine 'UCGENX_R'.
20240313/114504.075 - U00003422 WARNING: Cannot load conversation memory '0ce32a1b' for server routine 'UCGENX_R'.
20240313/114508.262 - U00003422 WARNING: Cannot load conversation memory '0ce32a34' for server routine 'UCGENX_R'.

Excerpt from the trace file 

04 - 20240313/113351.021 -  U00003422 WARNING: Cannot load conversation memory '0ce32a11' for server routine 'UCGENX_R'.
04 - 20240313/113351.021 -  U00009907 Memory view 'Input memory' (Address='000001552A9F9F20', Length='10528')
04 - 20240313/113351.021 -            00000000  45485155 49545420 30314C04 EF2C2400  >EHQUITT 01L.ﬤ.<
04 - 20240313/113351.021 -            00000010  00000000 4C044A4F 42532020 20200000  >....L.JOBS    ..<
04 - 20240313/113351.021 -            00000020  EF2C2400 73590F00 50424C55 2E58454E  >ﬤ.XX..XXXX.XXX<
04 - 20240313/113351.021 -            00000030  5449532E 412E4A4F 53512E4F 52412E41  >XXX.X.JOSQ.ORA.X<
04 - 20240313/113351.021 -            00000040  4E5A4148 4C5F5750 5F545820 20202020  >XXXX_XX_XX     <
04 - 20240313/113351.021 -            00000050= 20202020 20202020 20202020 20202020  >                <
04 - 20240313/113351.021 -            000000F0  00000000 BD10AB05 B010AB05 00000000  >....½.«.°.«.....<
04 - 20240313/113351.021 -            00000100  00000000 E8070300 0D000A00 21003000  >....议.....!.0.<
04 - 20240313/113351.021 -            00000110  00000000 6C070000 53514C4F 52413233  >....l...XXXXXXXX<

Environment

Automation Engine 21.0.9

Automation Engine 21.0.9 HF1

Automation Engine 21.0.9 HF2

Cause

Reproduction:

A SCRI (with generate-at-activation time) starts a JOB with ACTIVATE_UC_OBJECT(....WAIT)
This JOB has to be in an HOSTG without any active agent
The SCRI should wait for the JOB to finish (this was already not working)
After starting one agent in the HOSTG the JOB and the SCRI should finish
Here the forced trace occurred (also wrong)

Resolution

A problem has been solved, where forced traces (WARNING: Cannot load conversion memory) are created, when executing Jobs or Events on hostgroups without active Agents in the following versions.

Automation.Engine 21.0.10
Automation.Engine 24.1.0

Additional Information

The job specified in the traces can be removed to help prevent the issue as a temporary workaround.