Automic Workload Automation

 View Only
  • 1.  PerformanceLogger errors in AWI log

    Posted Jun 06, 2018 07:30 AM

    Every minute or so, the AWI log shows these messages:

    2018-06-06 11:23:48,527 pool-1-thread-1        [TRACE] NOSESSION/- NOUI   [ork.entrypoint.servlet.ECCServletService] - requestEnd null
    2018-06-06 11:23:48,527 pool-1-thread-1        [TRACE] NOSESSION/- NOUI   [rypoint.maintenance.SessionCleanupThread] - Ignoring expected NPE caused by request sometimes being null
    2018-06-06 11:24:34,656 http-nio-8080-exec-4   [TRACE] NOSESSION/- NOUI   [ork.entrypoint.servlet.ECCServletService] - requestStart com.vaadin.server.VaadinServletRequest@1dd598a
    2018-06-06 11:24:34,656 http-nio-8080-exec-4   [TRACE] UC4_EXP2:1/ABC1234/MYCOM NOUI 0000000003029230  [ork.entrypoint.servlet.ECCServletService] - requestEnd com.vaadin.server.VaadinServletRequest@1dd598a
    2018-06-06 11:24:34,939 http-nio-8080-exec-3   [TRACE] UC4_EXP2:1/ABC1234/MYCOM NOUI 0000000003029230  [ork.entrypoint.servlet.ECCServletService] - requestEnd com.vaadin.server.VaadinServletRequest@64b59baf
    2018-06-06 11:24:34,939 http-nio-8080-exec-3   [WARN ] UC4_EXP2:1/ABC1234/MYCOM NOUI 0000000003029230  [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.core.StandardEngineValve.invoke(StandardEngineValve.java:88)
            at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:620)
            at org.apache.catalina.valves.RemoteIpValve.invoke(RemoteIpValve.java:676)
            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.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1533)
            at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1489)
            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:748)
    2018-06-06 11:24:34,994 http-nio-8080-exec-9   [TRACE] NOSESSION/- NOUI   [ork.entrypoint.servlet.ECCServletService] - requestStart com.vaadin.server.VaadinServletRequest@4125aba8

    The messages do not appear to be associated with any problems in the AWI. As far as I can tell, the AWI is working fine. Is there a way to prevent these messages from appearing?



  • 2.  Re: PerformanceLogger errors in AWI log

    Posted Jun 06, 2018 08:41 AM

    Hi Michael,

    Have you seen KB article KB000087438 - Slow AWI performance on High Availability configuration:

    https://comm.support.ca.com/kb/slow-awi-performance-on-high-availability-configuration/kb000087438

     

    /Keld.



  • 3.  Re: PerformanceLogger errors in AWI log

    Posted Aug 14, 2018 07:54 PM

    I have the same issue. Tomcat 8.5.15.0, AWI 12.2.0.



  • 4.  Re: PerformanceLogger errors in AWI log
    Best Answer

    Posted Aug 15, 2018 04:43 AM

    I cannot remember where I got the answer to this, but I think it was from CA Support. The answer was that the errors could be safely ignored, and that they would be removed in a future AWI version.



  • 5.  Re: PerformanceLogger errors in AWI log

    Posted Jan 29, 2019 09:13 AM

    we get this error on tomcat 8.5 and tomcat 9 but on tomcat 7 we have not received this error.

    I think the problem seems to be caused by tomcat version.



  • 6.  RE: PerformanceLogger errors in AWI log

    Posted Mar 09, 2020 10:08 AM
    ​add/change following entry in configuration.properties, then the RuntimeException messages will not be written to the log anymore
    push.suspend.timeout=6000