Skip to content

RxResultSubscriber log noise: Broken pipe #14

Open
@alfanatico

Description

@alfanatico

RxResultSubscriber is logging an error at line 275 : log.error("Async Dispatch Error: ${e.message}", e).

When the user refreshes the browser, we see the following error with a large stack-trace:
2019-01-29 18:53:56.423 ERROR 6174 --- [ http-nio-8080-exec-4] o.g.plugins.rx.web.RxResultSubscriber : Async Dispatch Error: Broken pipe

However in line 278 it is using a debug level: log.debug("Async timeout occurred"). In both cases it seems that it is recovering from the error, and executing two lines of code:

asyncContext.request.removeAttribute(WebAsyncUtils.WEB_ASYNC_MANAGER_ATTRIBUTE) asyncContext.complete()

It seems that the system is recovering from above error conditions (in our use case we don't lose any event to the client, perhaps because the communication is being retried or established using a new connection). We would like to change the logging level to debug for both cases, just to avoid the log noise.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      pFad - Phonifier reborn

      Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

      Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


      Alternative Proxies:

      Alternative Proxy

      pFad Proxy

      pFad v3 Proxy

      pFad v4 Proxy