AWI 24.4.0: Slowness/reloading start page or HTTP Status 500/404

Products

• CA Automic Workload Automation - Automation Engine
• CA Automic One Automation

Issue/Introduction

Several issues have been detected when AWI 24.4.0 is not installed as a default Jetty deployment.

Example problems with non-standard deployments are:

• Slowness when AWI was installed on Tomcat 9
• Reloading of the AWI start page on Tomcat 9 
• Reloading of the AWI start page when using the parameter http.root on Jetty or renaming the awi.jar file on Tomcat 9 or 10
• ...

When the page is loaded, you may see a message like:

HTTP Status 404 – Not Found
The requested resource [/awi] is not available
The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.

OR

vaadinPush-min.js?v=…1b3803eff6abd965f:1 WebSocket connection to 'wss://jcp_server_name.example.com/AUTOMIC/VAADIN/push?v-r=push&v-uiId=…son;%20charset=UTF-8&X-atmo-protocol=true&X-Vaadin-LastSeenServerSyncId=23' failed: Error during WebSocket handshake: Unexpected response code: 501

OR

HTTP Status 500 – Internal Server Error

---

Type Exception Report

Message Connection refused: connect

Description The server encountered an unexpected condition that prevented it from fulfilling the request.

Exception

java.net.ConnectException: Connection refused: connect

Cause

This is a defect

Resolution

A fix for these problems is included in the AWI component for v24.4.0 HF2 (Available)