https://bz.apache.org/bugzilla/show_bug.cgi?id=64848
--- Comment #19 from Matt M ---
This is looking like a case where the remote endpoint is not able to respond
with its own close message.
We have seen 2 types of exception recorded in the Nio2SocketWrapper present in
the heap:
https://bz.apache.org/bugzilla/show_bug.cgi?id=64848
--- Comment #18 from Matt M ---
After a recent upgrade from 9.0.63 to 9.0.75 (with the 2 websocket fixes from
9.0.77 patched in) I am seeing some occurrences of the WsSession Object stuck
on the heap with state OUTPUT_CLOSED in
https://bz.apache.org/bugzilla/show_bug.cgi?id=64848
--- Comment #17 from zhougang ---
(In reply to Christopher Schultz from comment #16)
> (In reply to Vishwanath Karra from comment #15)
> > We are seeing this issue with 8.5.72 - is there some other patch needed for
> > the 8.5 codeline ? The
https://bz.apache.org/bugzilla/show_bug.cgi?id=64848
--- Comment #16 from Christopher Schultz ---
(In reply to Vishwanath Karra from comment #15)
> We are seeing this issue with 8.5.72 - is there some other patch needed for
> the 8.5 codeline ? The fix is confirmed for 9.0.40.
Are you sure it's
https://bz.apache.org/bugzilla/show_bug.cgi?id=64848
--- Comment #15 from Vishwanath Karra ---
We are seeing this issue with 8.5.72 - is there some other patch needed for the
8.5 codeline ? The fix is confirmed for 9.0.40.
--
You are receiving this mail because:
You are the assignee for the
https://bz.apache.org/bugzilla/show_bug.cgi?id=64848
--- Comment #14 from Christopher Schultz ---
Tomcat 9.0.40 started on 12 November[1]. Feel free to test and vote!
[1]
https://lists.apache.org/thread.html/rce32f696e12fecfd4b4383a5e8a389f4dac7d357053fd03ac7280868%40%3Cdev.tomcat.apache.org%3E
https://bz.apache.org/bugzilla/show_bug.cgi?id=64848
--- Comment #13 from Laszlo Karolyi ---
Hi Thomas,
According to the last information I got the Tomcat 9.0.40 release was estimated
to be ready this week but I haven't seen any update on this.
Since our internal release is still in progress
https://bz.apache.org/bugzilla/show_bug.cgi?id=64848
--- Comment #12 from Laszlo Karolyi ---
Ok, it sounds promising. Thanks for the quick feedback.
--
You are receiving this mail because:
You are the assignee for the bug.
-
https://bz.apache.org/bugzilla/show_bug.cgi?id=64848
--- Comment #11 from Mark Thomas ---
Soon. Need to resolve the remaining open issues then we can tag. Hopefully
early next week.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bz.apache.org/bugzilla/show_bug.cgi?id=64848
--- Comment #10 from Laszlo Karolyi ---
I couldn't find any information about the publication date of 9.0.40 but it
would help us if we knew when it is expected as we would include it in our next
release. Please let me know if you happen to
https://bz.apache.org/bugzilla/show_bug.cgi?id=64848
--- Comment #9 from Laszlo Karolyi ---
I can confirm that the issue I reported is indeed fixed in Tomcat 9.0.40 so
thanks for the quick remediation.
Do you happen to have an estimation as to when the 9.0.40 version of Tomcat is
expected to be
https://bz.apache.org/bugzilla/show_bug.cgi?id=64848
Mark Thomas changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REOPENED
https://bz.apache.org/bugzilla/show_bug.cgi?id=64848
Mark Thomas changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
https://bz.apache.org/bugzilla/show_bug.cgi?id=64848
--- Comment #6 from Laszlo Karolyi ---
After re-testing the reported scenario with 9.0.39 Tomcat version (core +
websocket) the WsSession objects still seem to get stuck on the heap.
Upon investigating the Tomcat source code a bit deeper it's
https://bz.apache.org/bugzilla/show_bug.cgi?id=64848
Mark Thomas changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEEDINFO
https://bz.apache.org/bugzilla/show_bug.cgi?id=64848
--- Comment #4 from Mark Thomas ---
I'm able to recreate this with the 3 provided Maven projects.
I ran the client on a local VM with VMware Workstation configured to limit the
network connection to 10Mbps with 20ms latency inbound and
https://bz.apache.org/bugzilla/show_bug.cgi?id=64848
--- Comment #3 from Mark Thomas ---
Actually, scratch that last comment. Tomcat detects that and will throw an
Exception. I'm still looking into this but there are changes between 9.0.36 and
9./0.39 that might help so that feedback would still
https://bz.apache.org/bugzilla/show_bug.cgi?id=64848
--- Comment #2 from Mark Thomas ---
The other thing to check is whether you have multiple threads writing to the
same WebSocket session concurrently. That is not supported by the Java
WebSocket API and could lead to the issue you describe.
--
https://bz.apache.org/bugzilla/show_bug.cgi?id=64848
Mark Thomas changed:
What|Removed |Added
OS||All
Status|NEW
19 matches
Mail list logo
