Is there a possibility that an open and active but orphaned CA Automic Web Interface (AWI) session will be terminated (Session timeout) automatically.
Article ID: 110198
Updated On:
Products
CA Automic Workload Automation - Automation Engine
Issue/Introduction
Is there a possibility that an open and active but orphaned CA Automic Web Interface (AWI) session will be terminated (Session timeout) automatically?
The Session Timeout can be set in Tomcat in the Web.xml. However, this setting has no effect on AWI.
This means that users who are logged in to AWI and leave the browser with AWI open the whole day but are doing nothing inside the application itself will never receive a Session expired message.
Environment
Release:
Component: AAUTWI
Component: AAUTWI
Resolution
If the users are just closing the browser after login there is a mechanism in place to cleanup the orphaned session within the CA Automic Workload Automation Engine (AE):
Inactive sessions (real idle sessions which end with closing the browser without logging out) will be cleaned up in regularly, defined timeframes.
After a defined amount of time (normally vaadin has a heartbeat interval of 5 minutes), after three times without the correct response, the session is recognized as orphaned and it will be closed therefore by our application.
This mechanism is not working in the case the user is still logged into the application since the Session is alive and active.
As soon as there is an open and therefore active session between AWI and AE there are many background activities which prevent the session timeout from being reached (e.g.: Refresh from Process Monitoring).
The session is active for the system even if the user does nothing in this session. This will never cause the set session timeout. The application currently cannot distinguish between "active but abandoned" and "active and in use".
Inactive sessions (real idle sessions which end with closing the browser without logging out) will be cleaned up in regularly, defined timeframes.
After a defined amount of time (normally vaadin has a heartbeat interval of 5 minutes), after three times without the correct response, the session is recognized as orphaned and it will be closed therefore by our application.
This mechanism is not working in the case the user is still logged into the application since the Session is alive and active.
As soon as there is an open and therefore active session between AWI and AE there are many background activities which prevent the session timeout from being reached (e.g.: Refresh from Process Monitoring).
The session is active for the system even if the user does nothing in this session. This will never cause the set session timeout. The application currently cannot distinguish between "active but abandoned" and "active and in use".
Additional Information
If the application should in the future react to a defined and customized session timeout, an Enhancement Request should be opened for this.
Please visit communities.ca.com (https://communities.ca.com/community/ca-automic-community/ca-automic-workload-automation) and open via new idea an enhancement request or vote for an existing one (https://communities.ca.com/community/ca-automic-community/ca-automic-workload-automation/content?filterID=contentstatus%5Bpublished%5D~category%5Bca-automic-workload-automation-english%5D)
Please visit communities.ca.com (https://communities.ca.com/community/ca-automic-community/ca-automic-workload-automation) and open via new idea an enhancement request or vote for an existing one (https://communities.ca.com/community/ca-automic-community/ca-automic-workload-automation/content?filterID=contentstatus%5Bpublished%5D~category%5Bca-automic-workload-automation-english%5D)
Feedback
Yes
No
Powered by
