https://bz.apache.org/bugzilla/show_bug.cgi?id=63210
--- Comment #16 from pazpeti ---
Thanks, it was working for me either :)
https://inspirecoding.app/
--
You are receiving this mail because:
You are the assignee for the bug.
https://bz.apache.org/bugzilla/show_bug.cgi?id=63210
--- Comment #15 from k...@gameldar.com ---
(In reply to Mark Thomas from comment #14)
> Improved fix applied (fixed versions as before).
I've built and tested with both the replication case and our use case with a
custom DataSource factory and
https://bz.apache.org/bugzilla/show_bug.cgi?id=63210
Mark Thomas changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REOPENED
https://bz.apache.org/bugzilla/show_bug.cgi?id=63210
Mark Thomas changed:
What|Removed |Added
Resolution|FIXED |---
Status|RESOLVED
https://bz.apache.org/bugzilla/show_bug.cgi?id=63210
--- Comment #12 from k...@gameldar.com ---
(In reply to Mark Thomas from comment #10)
> DBCP2 (actually Pool2) requires explicit shutdown and is documented as such.
> If it is shutdown (via closeMethod="close") then the Evictor thread is
>
https://bz.apache.org/bugzilla/show_bug.cgi?id=63210
Mark Thomas changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://bz.apache.org/bugzilla/show_bug.cgi?id=63210
--- Comment #10 from Mark Thomas ---
DBCP2 (actually Pool2) requires explicit shutdown and is documented as such. If
it is shutdown (via closeMethod="close") then the Evictor thread is stopped.
My current thinking is to set
https://bz.apache.org/bugzilla/show_bug.cgi?id=63210
--- Comment #9 from Mark Thomas ---
I am able to recreate the locally. Still investigating the root cause as I'd
expect the DataSource to be shutdown cleanly when the web application stops.
--
You are receiving this mail because:
You are the
https://bz.apache.org/bugzilla/show_bug.cgi?id=63210
--- Comment #8 from Mark Thomas ---
The proposed patch is not the correct solution. It addresses issue #1 in the
original description but the real problem appears to be issue #2. If issue #2
is fixed then issue #1 will be fixed too.
I'm
https://bz.apache.org/bugzilla/show_bug.cgi?id=63210
--- Comment #7 from Remy Maucherat ---
I was not aware the inline executor optimization was a 9.0 only feature, so the
big difference is actually there. To get the same deployment thread behavior on
Tomcat 9, you can enable parallel deployment
https://bz.apache.org/bugzilla/show_bug.cgi?id=63210
--- Comment #6 from k...@gameldar.com ---
Created attachment 36469
--> https://bz.apache.org/bugzilla/attachment.cgi?id=36469=edit
Patch that fixes this specific case with the EvictionTimer thread
--
You are receiving this mail because:
You
https://bz.apache.org/bugzilla/show_bug.cgi?id=63210
--- Comment #5 from k...@gameldar.com ---
Created attachment 36468
--> https://bz.apache.org/bugzilla/attachment.cgi?id=36468=edit
context configuration file for replication case
--
You are receiving this mail because:
You are the assignee
https://bz.apache.org/bugzilla/show_bug.cgi?id=63210
--- Comment #4 from k...@gameldar.com ---
Created attachment 36467
--> https://bz.apache.org/bugzilla/attachment.cgi?id=36467=edit
Example war for the replication case
--
You are receiving this mail because:
You are the assignee for the
https://bz.apache.org/bugzilla/show_bug.cgi?id=63210
--- Comment #3 from k...@gameldar.com ---
Created attachment 36466
--> https://bz.apache.org/bugzilla/attachment.cgi?id=36466=edit
Example servlet source to replicate the issue
--
You are receiving this mail because:
You are the assignee
https://bz.apache.org/bugzilla/show_bug.cgi?id=63210
--- Comment #2 from k...@gameldar.com ---
Created attachment 36465
--> https://bz.apache.org/bugzilla/attachment.cgi?id=36465=edit
Thread dump after Tomcat fails to stop
--
You are receiving this mail because:
You are the assignee for the
https://bz.apache.org/bugzilla/show_bug.cgi?id=63210
--- Comment #1 from k...@gameldar.com ---
Created attachment 36464
--> https://bz.apache.org/bugzilla/attachment.cgi?id=36464=edit
stacktrace showing servlet initialization in 9.0.16
--
You are receiving this mail because:
You are the
16 matches
Mail list logo
