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

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 Attachments: jboss-eap-native-5.0.0_BZ42728-windows32-i386.zip, jboss-eap-native-5.0.0_BZ42728-windows64-x86_64.zip, jbossnativebug.war 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.