ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

[AWI] Unexpected behavior when using an AWI pointing to 2 different AE systems in the same browser

book

Article ID: 196443

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine CA Automic Workload Automation - Automation Engine

Issue/Introduction

On AWI 12.3.3, the "Client" status get mixed when connecting to 2 different AE connection through the same AWI.

 

HOW TO REPRODUCE :

Using a single AWI called (awi_1233) that is configured to point to 2 different Automation Engine connections (called "RO123" and "RO1232").

E.g, in uc4config.xml (in this case, RO1232 & RO123 are installed on the same server, hence localhost) :

<connections>
        <connection name="RO1232" system="RO1232">
            <cp ip="localhost" port="2317"/>
            <cp ip="localhost" port="2318"/>
        </connection>
        <connection name="RO123" system="RO123">
            <cp ip="localhost" port="2217"/>
            <cp ip="localhost" port="2218"/>
        </connection>
</connections>

Reproduction steps :

  • On RO1232, connect on Client 0 (Administration mode), STOP the "Client 22"
  • On RO123, connect on Client 0 (Administration mode), check the "Client 22" status : make sure it is "Active"
  • On RO1232, connect on Client 22 and check if the message "Client 22 is inactive" is displayed. Also check in Administration -> Clients.
  • On RO123, connect on Client 22 and check if the message "Client 22 is inactive" is displayed. Also check in Administration -> Clients.

Expected behavior :

  • On RO1232 Client 22 : the message "Client inactive" should be displayed (since Client 22 has been stopped). The client should be visible as "Stopped" in Administration -> Clients.
  • On RO123 Client 22 : NO message should be displayed (since Client 22 is Active). The client should be visible as "Active" in Administration -> Clients.

Actual behavior :

  • On RO1232 Client 22 : the message "Client 22 is inactive" is displayed (expected, since Client 22 has been stopped). Client 22 is shown as "Inactive" in Administration -> Clients (expected)
  • On RO123 Client 22 : the message "Client 22 is inactive" is displayed (unexpected). Client 22 is shown as "Active" in Administration -> Clients (expected)

Cause

Bug

Environment

Release : 12.3

Component : AUTOMIC WEB INTERFACE

Resolution

Workaround : use a different browser or use the same one with the "Private" mode.

 

Fix : Will be fixed in a future release (TBD)

Powered by Wolken Software