Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RxResultSubscriber log noise: Broken pipe #14

Open
alfanatico opened this issue Feb 4, 2019 · 0 comments
Open

RxResultSubscriber log noise: Broken pipe #14

alfanatico opened this issue Feb 4, 2019 · 0 comments

Comments

@alfanatico
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant