After login via ECC receive "RuntimeException: This took too long" errors

book

Article ID: 84503

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine AUTOMIC WORKLOAD AUTOMATION

Issue/Introduction

Affects Release version(s): 11

Error Message :
The [TRACE] message contains the string "[com.uc4.webui.performance.framework] - Stacktrace for call. java.lang.RuntimeException: This took too long."

After logging into the Automation Engine system using the Enterprise Control Center (ECC) the following error messages are found in the <Hostname>_enterprise.control.center_LOG.00.txt file.
 
The [TRACE] message contains the string "[com.uc4.webui.performance.framework] - Stacktrace for call. java.lang.RuntimeException: This took too long."

This indicates that the request took longer than expected.
 
IIdentifiable is not implemented on null - but should be. Using classname as default, but this is not refactoring-safe", "[service.folder.FolderReadDelegateService] - No folder found at '' - root folder used instead." or "[e.interfaces.stubs.ClassNameIdentifiable] - IIdentifiable is not implemented on class com.automic.ecc.plugins.usermanagement.extensions.content.wizard.common.tabs.ae.authorizations.AuthorizationsController - but should be. Using classname as default, but this is not refactoring-safe

The login using ECC is successful even though these messages are displayed.

Cause

Cause type:
By design
Root Cause: These are just informational messages instead of error messages. They can be suppressed by changing the log levels.

Environment

OS Version: N/A

Resolution

This message:
 
The [TRACE] message contains the string "[com.uc4.webui.performance.framework] - Stacktrace for call. java.lang.RuntimeException: This took too long."

means that some requests took longer than expected.

You can turn these messages off by setting the correct log level in the logback.xml (default is DEBUG).

This message is an internal hint for development, in the latest 11.2 or 12.0 versions this message is already set to trace level

IIdentifiable is not implemented on null - but should be. Using classname as default, but this is not refactoring-safe", "[service.folder.FolderReadDelegateService] - No folder found at '' - root folder used instead." or "[e.interfaces.stubs.ClassNameIdentifiable] - IIdentifiable is not implemented on class com.automic.ecc.plugins.usermanagement.extensions.content.wizard.common.tabs.ae.authorizations.AuthorizationsController - but should be. Using classname as default, but this is not refactoring-safe"
 
To get rid of the error message you have to do the following:
  1. Create or edit the UC_CUSTOM_ATTRIBUTES on Client 0 and edit it as shown below:

<Please see attached file for image>

0EM0N000001hiks.png
  1. Then create a VARA.STATIC with the name CUSTOM_ATTR_BUSINESSUNITS and the following content:

<Please see attached file for image>

0EM0N000001hikx.png
  1. Then the error message should disappear in the logs.
  2. After that Tags can be added to the objects to be able to filter for them in the process monitoring perspective.

<Please see attached file for image>

0EM0N000001hil2.png
  1. This feature is often used to help distinguish between different departments in a company, but it is also useful in this situation.

    <Please see attached file for image>

    0EM0N000001hil7.png


Fix Status: No Fix

Fix Version(s):
N/A

Additional Information

Workaround :
N/A
 

Attachments

1558704526564000084503_sktwi1f5rjvs16llv.png get_app
1558704524564000084503_sktwi1f5rjvs16llu.png get_app
1558704522358000084503_sktwi1f5rjvs16llt.png get_app
1558704520157000084503_sktwi1f5rjvs16lls.png get_app