-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
[PinpiontWeb] fix a ActiveThread concurrency problem #1482
Comments
koo-taejin
added a commit
to koo-taejin/pinpoint
that referenced
this issue
Jan 26, 2016
1. changed to catched Excpetion Type in to throw WebSocketSession . (IOException -> Exception) 2. changed log level.
koo-taejin
added a commit
that referenced
this issue
Jan 26, 2016
[PinpiontWeb] fix a ActiveThread concurrency problem #1482
koo-taejin
added a commit
to koo-taejin/pinpoint
that referenced
this issue
Jan 29, 2016
1. added OrderedThreadPoolExecutor. 2. separated thread from WebSocketSessionId.
koo-taejin
added a commit
to koo-taejin/pinpoint
that referenced
this issue
Jan 30, 2016
add SimpleOrderedThreadPool pinpoint-apm#1482
koo-taejin
added a commit
to koo-taejin/pinpoint
that referenced
this issue
Jan 30, 2016
1. applied SimpleThreadPoolExecutor for separated thread from WebSocketSessionId.
koo-taejin
added a commit
to koo-taejin/pinpoint
that referenced
this issue
Oct 18, 2016
If webSocketSession status is not opened, then do not binding to flush aggregator.
koo-taejin
added a commit
that referenced
this issue
Oct 18, 2016
If webSocketSession status is not opened, then do not binding to flush aggregator.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If multiple threads invokes WebSocketSession's sendMessage method at the same time, ;
then it is possible to makes IllegalStateException.
The text was updated successfully, but these errors were encountered: