I met the same problem on Tomcat 9.0.74 these days and I think I have found the
answer.
Our case is:
1. Open serveral Chrome tabs and each tab establish a websocket connection and
a websocket session with Tomcat. To keep the connection and session alive,
there is a JS timer who send a STOMP heartb
I have spent some more time on this today and I am still unable to
recreate these results on either Linux or Windows using the Snake
WebSocket example that ships with Tomcat.
To make progress I need a reproducible test case, ideally using the
Tomcat examples from the latest release of any curr
Hi,
I've experienced the same issue as described on Apache Tomcat 10.1.13.
After downgrading to 10.1.5 it started to work correctly. I also inspected
the heapdump of the application with memory problems and found out that
there were many org.apache.tomcat.websocket.WsSession present in
OUTPUT_CLOS
Hi,
I've experienced the same issue as described on Apache Tomcat 10.1.13.
After downgrading to 10.1.5 it started to work correctly. I also inspected
the heapdump of the application with memory problems and found out that
there were many org.apache.tomcat.websocket.WsSession present in
OUTPUT_CLOS
On 20/08/2023 05:21, Mark Thomas wrote:
On 18/08/2023 11:28, Rubén Pérez wrote:
I started experiencing exactly the same issue when updating from Spring
6.0.7 to 6.0.9, therefore updating tomcat from 10.1.5 to 10.1.8. The
Memory
leak is very clearly visible in my monitoring tools. A further
On 18/08/2023 11:28, Rubén Pérez wrote:
This is a response to an existing thread (about Memory leak in recent
versions of Tomcat):
https://www.mail-archive.com/users@tomcat.apache.org/msg141882.html
I haven't found a way to reply publicly as a continuation of that thread.
You need to reply to
This is a response to an existing thread (about Memory leak in recent
versions of Tomcat):
https://www.mail-archive.com/users@tomcat.apache.org/msg141882.html
I haven't found a way to reply publicly as a continuation of that thread.
So here it goes what I am trying to say:
I started experiencing
I also spent quite some time already to create such a test case, but did not
yet manage to find something.
For now it works in Production to remove those dangling processes once per hour
(via bad reflection stuff ;-) ) … will try to add some logging to probably get
a grasp about what is going on
I've taken a look at the code and can't see how this might be happening.
I think a reproducible test case is going to be required to investigate
this further.
Mark
On 12/07/2023 09:25, Mark Thomas wrote:
Hi Mario,
That does look like a possible bug.
I'll try and do a code review before the
Hi Mario,
That does look like a possible bug.
I'll try and do a code review before the next release but from
experience f you are able to figure out how to reproduce it that would
help a lot.
Thanks,
Mark
On 06/07/2023 15:19, ma...@datenwort.at.INVALID wrote:
Hello!
I guess I found a me
Hello!
I guess I found a memory leak which I am not quite sure how to reproduce yet.
Our application is using WebSockets and sometimes it seems that Tomcat 9.0.75
does not always remove the „UpgradeProcessorInternal“ process from the list of
„waitingProcessors“ in „org.apache.coyote.AbstractProt
11 matches
Mail list logo
