Opening a Calendar (CALE) with about 1300 Calendar Events shows decrease in performance and lasts too long

Products

• CA Automic Workload Automation - Automation Engine
• AUTOMIC WORKLOAD AUTOMATION

Issue/Introduction

Error Message :
N/A

When opening a Calendar with roughly 1300 Calendar Events there is a decrease in performance which results in a Browser delay.

In the older Java User Interface (UI) this same transaction took seconds to open and edit.

In addition, a message is shown in the browsers header row (A web page page is slowing down your browser --> Option stop or wait)

<Please see attached file for image>

When looking at the Log files the following can be seen:
 

[WARN ] UC4K:104/YI00552/SECZ_BC NOUI 0000000072059232  [ork.entrypoint.servlet.ECCServletService] - 60.001s/60.001s [Request: GET /PUSH]java.lang.RuntimeException: This took too long.	at com.uc4.webui.performance.PerformanceLogger.log(PerformanceLogger.java:338)	at com.uc4.webui.performance.PerformanceLogger.done(PerformanceLogger.java:267)	at com.uc4.ecc.framework.entrypoint.servlet.ECCServletService.requestEnd(ECCServletService.java:115)	at com.vaadin.server.VaadinService.handleRequest(VaadinService.java:1436)	at com.vaadin.server.VaadinServlet.service(VaadinServlet.java:380)	at com.uc4.ecc.framework.entrypoint.servlet.main.MainApplicationServlet.service(MainApplicationServlet.java:147)	at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)	at org.apache.felix.http.base.internal.handler.ServletHandler.doHandle(ServletHandler.java:96)	at org.apache.felix.http.base.internal.handler.ServletHandler.handle(ServletHandler.java:79)	at org.apache.felix.http.base.internal.dispatch.ServletPipeline.handle(ServletPipeline.java:42)	at org.apache.felix.http.base.internal.dispatch.InvocationFilterChain.doFilter(InvocationFilterChain.java:49)	at org.apache.felix.http.base.internal.dispatch.HttpFilterChain.doFilter(HttpFilterChain.java:33)	at org.apache.felix.http.base.internal.dispatch.FilterPipeline.dispatch(FilterPipeline.java:48)	at org.apache.felix.http.base.internal.dispatch.Dispatcher.dispatch(Dispatcher.java:39)	at org.apache.felix.http.base.internal.DispatcherServlet.service(DispatcherServlet.java:67)	at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)	at org.apache.felix.http.proxy.ProxyServlet.service(ProxyServlet.java:60)	at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:292)	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207)	at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:240)	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207)	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:212)	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:94)	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:504)	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:141)	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79)	at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:620)	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:88)	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:502)	at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1132)	at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:684)	at org.apache.tomcat.util.net.AprEndpoint$SocketProcessor.doRun(AprEndpoint.java:2521)	at org.apache.tomcat.util.net.AprEndpoint$SocketProcessor.run(AprEndpoint.java:2510)	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)	at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)	at java.lang.Thread.run(Thread.java:745)

This behavior can be seen in different Browsers such as:

Chrome: 20min
Opera: 20 mmin
MS Edge: 7min
Firefox: 1 min

Comparing this to the JAVA UI --> 5 secs.

 

Cause

Cause type:
Defect
Root Cause: When opening a calendar with roughly 1300 Calendar Events there is a decrease in performance and results in Browser delay.

Environment

Release: AUTWAB99000-12.0-Automic Workload Automation-Base Edition
Component:

Resolution

Update to a fix version listed below or a newer version if available, where we now support lazy loading of calendar events which will no longer freeze the browser.
 

Fix Status: In Progress

Fix Version(s):
Automic Web Interface - 12.2.0 - Planned release date: 2018-06-19
Automic Web Interface - 12.1.1 - already released

Additional Information

Workaround :
N/A