ssl_request_log generating large numbers of /awi/PUSH calls

book

Article ID: 197272

calendar_today

Updated On:

Products

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

Issue/Introduction

In reviewing the ssl_request_log, there may be large numbers of entries similar to:

12.34.56.789 - [04/Aug/2020:10:32:35 -0400] "GET /awi/PUSH?v-uiId=0&v-pushId=e615093e-d1f8-4f0b-8f9d-947374158414&X-Atmosphere-tracking-id=2357a3a1-c052-45dd-b253-a06f193d9a08&X-Atmosphere-Framework=2.2.13.vaadin5-javascript&X-Atmosphere-Transport=long-polling&X-Atmosphere-TrackMessageSize=true&Content-Type=application%2Fjson%3B%20charset%3DUTF-8&X-atmo-protocol=true&_=1596551555973 HTTP/1.1" 200 152 687 "https://automic.awi.com/awi/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.89 Safari/537.36"


Environment

Release : 12.3

Component : AUTOMIC WEB INTERFACE

Resolution

These messages are generated as a function of that version of Tomcat (8.5) requiring long polling versus Websockets; upgrading to Tomcat 9 should minimize their generation

If the messages are still occurring after updating Tomcat, one or all of the following options should be considered:

  1. Enable websocket communication in their network.  Please note this requires network admins and is not the same as enabling websockets within Tomcat.  If the network does not allow them, then Tomcat falls back to long-polling
  2. Implement tomcat log rotation.  This will need to be done by a Tomcat administrator, Broadcom does not have recommendations on how to do this
  3. Another option to further decrease the log usage would be to increase the heartbeat interval to (example 120s). More info on this is described in article 214083