Version 5 does not reconnect to Automation Engine after failure

book

Article ID: 87553

calendar_today

Updated On:

Products

CA Continuous Delivery Automation - Automation Engine

Issue/Introduction

Affects Release version(s): 5

Error Message :
Error in ECC log:
com.uc4.ecc.backends.impl.dataservice.connection.ConnectionService - Connection to Automation Engine failed
at 'ecc.com:2217'.
java.io.IOException: Connection reset by peer

Unable to log into ARA after the Automation Engine (AE) goes down and is brought back up.

When logging in using ECC, the Release Manager plugin will communicate with ARA to check for an available (already logged in) user and load/unload the perspective accordingly.

In ARA 5/5.1, when it disconnects from AE for any reason (AE went down, network issue, etc), it does not automatically reconnect and the user can not be authenticated. This blocks the checking progress of the Release Manager plugin. 

This behavior has been redesigned in versions 6 and 7, and the reconnect is now done automatically. 

 

Cause

Cause type:
By design
Root Cause: In ARA 5/5.1 when AE disconnects for whatever reason the release manager plugin will not automatically reconnect so user can't be authenticated until ARA is restarted.

Environment

Release:
Component: ARLSMG

Resolution

This field was added on 30/03/2017. This article has not been updated yet. Refer to the "Description" or "Workaround" sections for solution information.

Fix Status: Released

Fix Version(s):
Release Manager 7.0 - Available
Release Manager 6.0 - Available

Additional Information

Workaround :
Restart ARA or restart the ARA machine.