[jboss-jira] [JBoss JIRA] Commented: (JBWEB-101) Thread handle leak using Jboss Web native connectors on Windows
[
https://jira.jboss.org/jira/browse/JBWEB-101?page=com.atlassian.jira.plug...
]
Sebastian Otaegui commented on JBWEB-101:
-----------------------------------------
--------------------------------------
Handle = 0x000018c0 - OPEN
Thread ID = 0x00028cd4, Process ID = 0x00029c40
0x56f4624c: libapr_1!apr_os_thread_current+0x0000003c
0x57112bf2: LIBEAY32!ERR_remove_state+0x00000062
0x5a61899f: verifier!AVrfpStandardDllEntryPointRoutine+0x0000014f
0x7c81a352: ntdll!LdrpCallInitRoutine+0x00000014
0x7c819178: ntdll!LdrShutdownThread+0x000000d2
0x77e4f930: kernel32!ExitThread+0x0000002f
0x5a6149ff: verifier!AVrfpExitThread+0x0000004f
0x7c3494f5: msvcr71!_endthreadex+0x00000030
0x5a614cc0: verifier!AVrfpStandardThreadFunction+0x00000060
0x77e6482f: kernel32!BaseThreadStart+0x00000034
--------------------------------------
Handle = 0x00001f44 - OPEN
Thread ID = 0x0002bd7c, Process ID = 0x00029c40
0x56f4624c: libapr_1!apr_os_thread_current+0x0000003c
0x57112bf2: LIBEAY32!ERR_remove_state+0x00000062
0x5a61899f: verifier!AVrfpStandardDllEntryPointRoutine+0x0000014f
0x7c81a352: ntdll!LdrpCallInitRoutine+0x00000014
0x7c819178: ntdll!LdrShutdownThread+0x000000d2
0x77e4f930: kernel32!ExitThread+0x0000002f
0x5a6149ff: verifier!AVrfpExitThread+0x0000004f
0x7c3494f5: msvcr71!_endthreadex+0x00000030
0x5a614cc0: verifier!AVrfpStandardThreadFunction+0x00000060
0x77e6482f: kernel32!BaseThreadStart+0x00000034
Thread handle leak using Jboss Web native connectors on Windows
---------------------------------------------------------------
Key: JBWEB-101
URL: https://jira.jboss.org/jira/browse/JBWEB-101
Project: JBoss Web
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: JBossWeb-1.0.1.GA
Reporter: Mike Poindexter
Assignee: 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-l...).
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira