Jenkins log flooded with SSE gateway plugins related warnings

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major
    • Component/s: sse-gateway-plugin
    • Environment:
      Jenkins version: 2.190.1, Server Sent Events (SSE) Gateway Plugin version: 1.20

      Hi,

      Jenkins log is flooded with below warnings. Can you please help to fix the issue.Ā  Please let me know if any additional information is needed from my end.

      Jan 23, 2020 7:37:19 PMĀ SEVEREĀ org.jenkinsci.plugins.ssegateway.sse.EventDispatcher dispatchReload
      Unable to send reload event to client. java.lang.IllegalStateException: The request associated with the AsyncContext has already completed processing. at org.apache.catalina.core.AsyncContextImpl.check(AsyncContextImpl.java:509) at org.apache.catalina.core.AsyncContextImpl.getResponse(AsyncContextImpl.java:227) at org.jenkinsci.plugins.ssegateway.sse.AsynchEventDispatcher.getResponse(AsynchEventDispatcher.java:104) at org.jenkinsci.plugins.ssegateway.sse.EventDispatcher.dispatchEvent(EventDispatcher.java:170) at org.jenkinsci.plugins.ssegateway.sse.EventDispatcher.dispatchReload(EventDispatcher.java:337) at org.jenkinsci.plugins.ssegateway.sse.EventDispatcher.processRetries(EventDispatcher.java:394) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)

            Assignee:
            Olivier Lamy
            Reporter:
            Ganesh Saraf
            Votes:
            2 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: