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.

AWA: Why is it possible that a working AWI can not log in, but a Java UI can?

book

Article ID: 188151

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

In situations where there is undue load or unexpected behavior on the system, it may be possible that the Automic Web Interface is unable to log in, but the Java User Interface is still able to. 

Cause

Difference in behavior between Java UI and Automic Web Interface

Environment

Release : 12.3

Component : AUTOMIC WEB INTERFACE

Resolution

When establishing a connection with the Automation Engine, the Automic Web Interface performs additional checks that place entries into the MQWP tables. If you are in a situation where the MQWP tables are overloaded or processing slowly, this could cause a timeout.

As the Java UI does not perform these checks, it is able to complete the connection and sign in; this does not mean that the core issue (MQWP table size) isn't present, just that the checks do not cause a timeout.