Old connections in JCP are not automatically closed

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

The JCP connections are not closed automatically after the AWI user closes the browser tab so they remain active at the JCP level and can be visible in the menu Administration - User Management -Connections on AWI, ordering by the "Last Seen" timestamp.

Expected Behavior: After closing the browser brutally or just the tab without logout, after several minutes the JCP should close these dead connections
Actual Behavior: Some AWI connections remain Established at JCP level forever.

 

This reproduces only on Tomcat AWI but not on Jetty AWI, see below the reproduction steps:
1. Login to AWI - Client 0 (to monitor sessions)
2. Login to AWI - Client X - another browser
2.1 Click something, then close tab (note the time)
3 In Client 0, go to Connections. hit refresh after a while.
3.1 Connection/User AWI session does not close at all - stays listed which is not OK.

The AWI Restart or JCP restart seems to clear the connections.

Explicit log-off also triggers a session clear.

Environment

Release : 12.3.x and 21.x

Component: Automation Engine

Sub-Component: Automic Web Interface (AWI) on Tomcat only

Cause

Defect in AWI

Resolution

Workaround:

Click on Disconnect User in the menu Connections on AWI, ordering by the "Last Seen" timestamp, if older than a day they can be disconnected.

Solution:

Update to a fix version listed below or a newer version if available.

Fix version:
Component(s): Automic.Web.Interface (AWI)
Automation.Engine 21.0.7 - Available

Additional Information

Defect Number: AE-31681

Solution Details: A problem has been solved where JCP connections have not been correctly closed even when the User actively did so (e.g. by closing the AWI browser tab).