[jboss-jira] [JBoss JIRA] Created: (JBWEB-101) Thread handle leak using Jboss Web native connectors on Windows

Wed Mar 12 13:06:03 EDT 2008

Thread handle leak using Jboss Web native connectors on Windows
---------------------------------------------------------------

                 Key: JBWEB-101
                 URL: http://jira.jboss.com/jira/browse/JBWEB-101
             Project: JBoss Web
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions:  JBoss Web Server 1.0.1 GA
            Reporter: Mike Poindexter
         Assigned To: Mladen Turk

When running JBossWeb using the native connectors under Windows XP/Win2k3 I'm seeing a Thread Handles leak.  I've traced this with the !htrace feature of CDB (like at http://blogs.technet.com/brad_rutkowski/archive/2007/11/13/got-a-handle-leak-use-htrace-to-help-find-the-leaking-stacks-non-invasively.aspx).  It appears as though this is the behavior reported at https://issues.apache.org/bugzilla/show_bug.cgi?id=42728.  The native stack trace from the leaked handles looks like:

Handle = 0x00000c64 - OPEN
Thread ID = 0x00001014, Process ID = 0x00003e44

0x2c2d624c: libapr_1!apr_os_thread_current+0x0000003c
0x2c339202: LIBEAY32!ERR_remove_state+0x00000062
0x7c9011a7: ntdll!LdrInitializeThunk+0x00000029
0x7c919213: ntdll!LdrShutdownThread+0x000000ed
0x7c80c096: kernel32!ExitThread+0x0000003e
0x7c87545b: kernel32!GetConsoleCharType+0x000002a8
0x7c80b683: kernel32!GetModuleFileNameA+0x000001b4

>From what I can tell, the end result is that one thread handle leaks per JVM thread that terminates.  Over the course of a long running server application, this becomes a major leak.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira