[Bug 69608] JSP Servlet engine is garbage collected leading to Denial of service

2025-03-28 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69608 Mark Thomas changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|---

[Bug 69608] JSP Servlet engine is garbage collected leading to Denial of service

2025-03-21 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69608 --- Comment #10 from John Engebretson --- That makes sense - accumulating orphaned threads are a good way to run out of memory, and you're right that the fix is to not orphan the threads. At this point I'd suggest thread dumps on an affected s

[Bug 69608] JSP Servlet engine is garbage collected leading to Denial of service

2025-03-21 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69608 --- Comment #9 from Praddy --- I started two instances of Tomcat, instance A as the web server having only the JSP and servlets and instance B having the application logic code. The logic codes starts threads to fetch mails but the threads hang

[Bug 69608] JSP Servlet engine is garbage collected leading to Denial of service

2025-03-18 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69608 --- Comment #8 from Mark Thomas --- Just noting it has been a week since the request for evidence in comment #1 Without supporting evidence, this issue is heading towards a "works for me" resolution. -- You are receiving this mail because: Y

[Bug 69608] JSP Servlet engine is garbage collected leading to Denial of service

2025-03-17 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69608 --- Comment #7 from John Engebretson --- I agree with others that this probably isn't caused by an error in Tomcat - Tomcat directly allocates a relatively small amount of memory, so whatever is creating the GC demand is most likely application

[Bug 69608] JSP Servlet engine is garbage collected leading to Denial of service

2025-03-12 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69608 --- Comment #6 from Chen Jp --- Could try CATALINA_OPTS="-Xms10g -Xmx10g"? -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail:

[Bug 69608] JSP Servlet engine is garbage collected leading to Denial of service

2025-03-10 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69608 --- Comment #3 from Remy Maucherat --- Also, the link taks about GC pauses. This is normal behavior, although of course this can impact the response times for Tomcat and as a result this requires fine tuning to avoid. However, here the claim i

[Bug 69608] JSP Servlet engine is garbage collected leading to Denial of service

2025-03-10 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69608 --- Comment #4 from Praddy --- (In reply to Christopher Schultz from comment #2) > No Java version mentioned, no GC settings mentioned. I'm using OpenJDK 21, I did not mention any GC(which defaults to G1GC) in the options just used -Xms2g -Xmx6

[Bug 69608] JSP Servlet engine is garbage collected leading to Denial of service

2025-03-10 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69608 Mark Thomas changed: What|Removed |Added Status|NEW |NEEDINFO Severity|critical

[Bug 69608] JSP Servlet engine is garbage collected leading to Denial of service

2025-03-10 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69608 --- Comment #2 from Christopher Schultz --- No Java version mentioned, no GC settings mentioned. This is not really a valid report. Tomcat does not have any direct control over when and how Garbage Collection activities occur within the Java

[Bug 69608] JSP Servlet engine is garbage collected leading to Denial of service

2025-03-10 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=69608 --- Comment #5 from Praddy --- (In reply to Remy Maucherat from comment #3) > Also, the link taks about GC pauses. This is normal behavior, although of > course this can impact the response times for Tomcat and as a result this > requires fine