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

Issue #5193 - Adding more WebSocket EventDriver logging #5202

Closed

Conversation

joakime
Copy link
Contributor

@joakime joakime commented Aug 26, 2020

In an effort to better understand the behaviors reported at Issue #5193, more logging at the EventDriver layer has been added.

This is a Draft PR, and isn't suitable for merge until it's been thoroughly discussed (pros and cons).

Signed-off-by: Joakim Erdfelt joakim.erdfelt@gmail.com

Signed-off-by: Joakim Erdfelt <joakim.erdfelt@gmail.com>
Copy link
Contributor

@lachlan-roberts lachlan-roberts left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It might help to have some logging in the MessageAppender classes as well.

if (LOG.isDebugEnabled())
{
if (message == null)
LOG.debug("onTextMessage(<null>) - events.onText={}", events.onText);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is not possible to have a null message here, it can be empty string but not null.

Signed-off-by: Joakim Erdfelt <joakim.erdfelt@gmail.com>
@lachlan-roberts
Copy link
Contributor

Merged these changes into PR #5208

@joakime joakime deleted the jetty-9.4.x-5193-better-websocket-event-logging branch September 2, 2020 15:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants