You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2009/05/20 15:43:55 UTC

DO NOT REPLY [Bug 47227] New: Executor "namePrefix" property not working well

https://issues.apache.org/bugzilla/show_bug.cgi?id=47227

           Summary: Executor "namePrefix" property not working well
           Product: Tomcat 6
           Version: 6.0.18
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Connectors
        AssignedTo: dev@tomcat.apache.org
        ReportedBy: thierry.leveque@vantrix.com


When setting a "namePrefix" to an Executor in server.xml, new threads in the
pool do not always use the given name prefix.

For my tests I used this descriptor:
<Executor name="VanExecutor" namePrefix="VanMx6Mn1-STI" maxThreads="6"
minSpareThreads="1" maxIdleTime="10000" daemon="false" />

The executor is assigned to my http connector:
<Connector port="8700" executor="VanExecutor" enableLookups="false"
allowTrace="true" vanAdditionalParams="here" maxThreads="200" acceptCount="20"
connectionTimeout="60000" bufferSize="4096" disableUploadTimeout="true"
maxProcessors="10" minProcessors="5" />

When I start my server and look with jconsole (or jstack), I can see that the
first thread is really using my defined prefix. But most of the subsequent
threads use the name "Null_Thread_Name".
I said "most" because sometime I see my prefix used again correctly but only
when using a large amount of threads (i.e. max 200 min 100).

I am using jdk 1.6.012.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org

DO NOT REPLY [Bug 47227] Executor "namePrefix" property not working well

Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=47227

Mark Thomas <ma...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WORKSFORME

--- Comment #1 from Mark Thomas <ma...@apache.org> 2009-09-16 22:46:25 BST ---
I can't reproduce this with trunk or 6.0.x. I have checked the code and the
text "Null_Thread_Name" does not appear any where in the 6.0.x source.

I also can't see, given the thread creation code, how a thread could end up
with a null thread name.

The only possibility I can think of is a JVM bug but there isn't much evidence
of that.

Given that this can't be reproduced and a source code review shows no obvious
cause, I am resolving this as works for me.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org