AWI logs - warnings

book

Article ID: 223613

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine CA Automic One Automation

Issue/Introduction

This article will try to give you more information regarding WARN messages written out in the AWI logs.

Some of these messages may include:

pool-2-thread-1043     [WARN ] AUTOMIC:100/AUTOMIC/AUTOMIC 437 0000000001000453  [rk.core.pool.ContextAwareExecutorService] - This took too long. 0.000s/31.463s [Request: null]
2021-06-10 11:14:09,387 http-nio-8080-exec-6   [INFO ] AUTOMIC:100/AUTOMIC/AUTOMIC 437 0000000001000453  [commons.controls.contextmenu.ContextMenu] - Opening child context menu for com.uc4.e[email protected]2f637f8e
2021-06-10 11:14:09,840 http-nio-8080-exec-10  [INFO ] AUTOMIC:100/AUTOMIC/AUTOMIC 437 0000000001000453  [commons.controls.contextmenu.ContextMenu] - Opening child context menu for [email protected]
2021-06-10 11:14:10,105 http-nio-8080-exec-3   [INFO ] AUTOMIC:100/AUTOMIC/AUTOMIC 437 0000000001000453  [commons.controls.contextmenu.ContextMenu] - Opening child context menu for [email protected]

 

 

 

Cause

This is normal logging behavior when the application is running. AWI is functioning as expected, but if you are looking in the logs, you will see these message.

 

 

Environment

Release : 12.3

Component : AUTOMATION ENGINE

Tomcat 8 or 9

Resolution

At its simplest, these don't really mean anything. 

The logging for Tomcat utilizes something called Mapped Diagnostic Context. What this does is allow the deployed applications to provide more exacting messages, especially at an INFO, DEBUG, or TRACE level of logging, in order to better find where a problem may be.

What this does at the higher levels (WARN, ERROR) is add more messages to the output. They don't mean there is any issue or that it is foreshadowing an issue, it's literally just writing out pretty much everything it's doing. 

At the highest level, you could set the levels to OFF, but this is not recommended at all.
It won't stop everything, but it won't catch a problem either.
If you turn off logging, then if you do run into an issue there will be nothing to review in order to assist in locating the problem. 

These are harmless messages. These messages are written out, but processing continues as normal. You aren't seeing the entire picture of what may be happening because there isn't a logging context for every single method invoked.

A lot of logging happens that doesn't indicate a problem. Even ERROR level messages don't necessarily mean there is a problem.

But if you don't know what the message is and you have questions, please contact support.