https://bz.apache.org/bugzilla/show_bug.cgi?id=58624
cameraezviz changed:
What|Removed |Added
URL||https://ngaydem.vn/tin-tuc/
https://bz.apache.org/bugzilla/show_bug.cgi?id=58624
--- Comment #19 from cameramamnon ---
Kính gửi: Quý Khách hàng!
Lời đầu, Công ty Cổ phần phát triển công nghệ Ngày Đêm (Ngày Đêm) xin gửi đến
Quý Khách hàng lời chúc sức khỏe, thành công và thịnh vượng. Ngày Đêm xin cảm
ơn Quý Khách hàng đã tín
https://bz.apache.org/bugzilla/show_bug.cgi?id=58624
pcccngaydem changed:
What|Removed |Added
URL||http://pcccngaydem.vn/
Keyword
https://bz.apache.org/bugzilla/show_bug.cgi?id=58624
--- Comment #17 from SAIRAM NATARAJAN ---
Using tomcat version 8.0.38. Seeing the block on sendText message indefinitely.
"pool-2-thread-2" #26 prio=5 os_prio=0 tid=0x0bc22c00 nid=0x5ca7 waiting for
monitor entry [0x8636f000]
java.lang.Thre
https://bz.apache.org/bugzilla/show_bug.cgi?id=58624
--- Comment #16 from Mark Thomas ---
This new issue is being tracked under bug 59014
--
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscri
https://bz.apache.org/bugzilla/show_bug.cgi?id=58624
--- Comment #15 from Sebastian Herold
---
+1 for reopening the case or creating a new bug, if this (java.io.IOException:
Unable to write the complete message as the WebSocket connection has been
closed) is not related to the existing bug.
Spr
https://bz.apache.org/bugzilla/show_bug.cgi?id=58624
--- Comment #14 from Barry Coughlan ---
Should I change this to reopened just so this isn't forgotten about?
--
You are receiving this mail because:
You are the assignee for the bug.
--
https://bz.apache.org/bugzilla/show_bug.cgi?id=58624
--- Comment #13 from Barry Coughlan ---
Hi Mark,
I was writing a test case for bug57489 and came across a problem with
session.close() that I think is related to this fix. Since session.close() sets
state = State.CLOSING the block in registerF
https://bz.apache.org/bugzilla/show_bug.cgi?id=58624
--- Comment #12 from Barry Coughlan ---
Created attachment 33320
--> https://bz.apache.org/bugzilla/attachment.cgi?id=33320&action=edit
Test to check that session.close() does not call OnError
--
You are receiving this mail because:
You are
https://bz.apache.org/bugzilla/show_bug.cgi?id=58624
Mark Thomas changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bz.apache.org/bugzilla/show_bug.cgi?id=58624
--- Comment #10 from Barry Coughlan ---
(In reply to Mark Thomas from comment #9)
> Thanks for the great analysis and test case. I've fixed this in 9.0.x for
> 9.0.0.M2. There has been some refactoring of the relevant code so a
> back-port may
https://bz.apache.org/bugzilla/show_bug.cgi?id=58624
--- Comment #9 from Mark Thomas ---
Thanks for the great analysis and test case. I've fixed this in 9.0.x for
9.0.0.M2. There has been some refactoring of the relevant code so a back-port
may take a little longer than usual.
--
You are receiv
https://bz.apache.org/bugzilla/show_bug.cgi?id=58624
Mark Thomas changed:
What|Removed |Added
Status|NEEDINFO|NEW
--- Comment #8 from Mark Thomas ---
https://bz.apache.org/bugzilla/show_bug.cgi?id=58624
--- Comment #7 from Barry Coughlan ---
(In reply to Mark Thomas from comment #6)
> Thanks for all the work on this.
>
> It is worth updating to the latest 8.0.x in case one of the I/O or
> concurrency updates has improved this.
>
> I'm switch
https://bz.apache.org/bugzilla/show_bug.cgi?id=58624
Mark Thomas changed:
What|Removed |Added
Status|NEW |NEEDINFO
--- Comment #6 from Mark Thomas
https://bz.apache.org/bugzilla/show_bug.cgi?id=58624
--- Comment #5 from Barry Coughlan ---
The race condition I was talking about was incorrect, as the if (!close) in
endMessage() takes care of it. Also the exceptions are logged because the
executor is called with execute() instead of submit().
https://bz.apache.org/bugzilla/show_bug.cgi?id=58624
--- Comment #4 from Barry Coughlan ---
(In reply to Christopher Schultz from comment #3)
> (In reply to Barry Coughlan from comment #2)
> > My current working theory for what's happening is as follows:
> > - Server starts sending a message
> >
https://bz.apache.org/bugzilla/show_bug.cgi?id=58624
--- Comment #3 from Christopher Schultz ---
(In reply to Barry Coughlan from comment #2)
> My current working theory for what's happening is as follows:
> - Server starts sending a message
> - The client closes the connection before the execut
https://bz.apache.org/bugzilla/show_bug.cgi?id=58624
--- Comment #2 from Barry Coughlan ---
Sorry for all the noise.
If I understand correctly, the flow of sending messages goes like this:
WsRemoteEndpointImplBase.startMessage -> messaged dispatched to
WsServerContainer.executor -> calls WsRemo
https://bz.apache.org/bugzilla/show_bug.cgi?id=58624
Barry Coughlan changed:
What|Removed |Added
OS||All
--- Comment #1 from Barry Coughla
20 matches
Mail list logo
