https://issues.apache.org/bugzilla/show_bug.cgi?id=50306
--- Comment #7 from TomLu 2010-12-29 05:02:04 EST ---
Created an attachment (id=26451)
--> (https://issues.apache.org/bugzilla/attachment.cgi?id=26451)
Patch for Tomcat's ThreadPoolExecutor
WebSphere has hung/stuck thread detection logic
https://issues.apache.org/bugzilla/show_bug.cgi?id=50527
Summary: misleading error message for unknown message
Product: Tomcat 6
Version: 6.0.29
Platform: PC
Status: NEW
Severity: normal
Priority: P2
Component: Cat
https://issues.apache.org/bugzilla/show_bug.cgi?id=50527
Konstantin Kolinko changed:
What|Removed |Added
Summary|misleading error message|misleading error message
May I suggest you emit a warning to the logs when comma is used in the
regexp for a few versions?
Hen
On Fri, Dec 24, 2010 at 10:34 AM, Mark Thomas wrote:
> There are a number of configuration properties defined as "comma
> separated regular expressions". As someone pointed out at at ApacheCon
>
Author: rjung
Date: Wed Dec 29 20:42:04 2010
New Revision: 1053727
URL: http://svn.apache.org/viewvc?rev=1053727&view=rev
Log:
Improve documentation of database connection factory.
Modified:
tomcat/trunk/webapps/docs/changelog.xml
tomcat/trunk/webapps/docs/jndi-resources-howto.xml
Modifi
https://issues.apache.org/bugzilla/show_bug.cgi?id=50306
--- Comment #8 from Pid 2010-12-29 16:47:42 EST ---
If I understand the patch correctly, I disagree with the idea of an arbitrary
(even if configurable) time threshold per thread.
A long running thread is not necessarily a broken one; ther
