I wanted to let everyone know that I figured this out -- sort of.
Seems I was trying this logged in using Remote Desktop (MS) while logged
in as a user that wasn't Administrator, though part of the admin group.
Something about that configuration is causing the error.
When I went to the console, I w
> -Original Message-
> From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com]
> Sent: Tuesday, October 12, 2010 12:28 PM
> To: Tomcat Users List
> Subject: RE: Error getting Thread dump on Windows
>
> > From: Jeffrey Janner [mailto:jeffrey.jan...@polyd
> From: Jeffrey Janner [mailto:jeffrey.jan...@polydyne.com]
> Subject: RE: Error getting Thread dump on Windows
> Just need to know what's up with the Windows error when
> taking a stack dump.
Likely because the account used for the service has very restricted
capabilitie
11:58 AM
> To: Tomcat Users List
> Subject: RE: Error getting Thread dump on Windows
>
> I can use Process Explorer at the windows level to get the Windows
> stack
> of what appears to be the runaway thread:
> ntkrnlpa.exe+0x8db2e
> ntkrnlpa.exe+0x29a82
> ntkrnlpa.exe+
I can use Process Explorer at the windows level to get the Windows stack
of what appears to be the runaway thread:
ntkrnlpa.exe+0x8db2e
ntkrnlpa.exe+0x29a82
ntkrnlpa.exe+0x331a4
hal.dll+0x6199
hal.dll+0x63d9
hal.dll+0x6577
hal.dll+0x3902
jvm.dll!AsyncGetCallTrace+0x3baf0
The thread is using about
