tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Konstantin Kolinko <knst.koli...@gmail.com>
Subject Re: Windows Thread dump issue
Date Wed, 20 Jan 2010 18:04:43 GMT
2010/1/20 Caldarale, Charles R <Chuck.Caldarale@unisys.com>:
>> From: Konstantin Kolinko [mailto:knst.kolinko@gmail.com]
>> Subject: Re: Windows Thread dump issue
>>
>> Look in stdout_xxxx.log.  I don't have 5.5 installed at the moment,
>> but in 6.0 it is there.
>
> Not for me - it's in jakarta_service_yyyyMMdd.log, in both 5.5 and 6.0.
>
>  - Chuck
>

2010/1/20 Caldarale, Charles R <Chuck.Caldarale@unisys.com>:
>> From: Jeffrey Janner [mailto:Jeffrey.Janner@PolyDyne.com]
>> Subject: Windows Thread dump issue
>>
>> I have a Windows 2008 Server 64-bit running Sun JDK 1.6.0_13 64-bit and
>> Tomcat 5.5.27.
>
> I just tried it with Vista 64 using JDK 1.6.0_14, running both Tomcat 5.5.27 and 6.0.20.
>

With 6.0.20 it ends up in jakarta_service_20100120.log, the service
runner version there is 2.0.4.

With 6.0.24 RC it ends up in stdout_20100120.log, the service runner
version there is 2.0.6.

Both on the same PC with JRE 6u17 and WinXP 32-bit.


>From a quick look at the procrun sources svn history, I do not see any
specific commit that might have caused this change.  And from last
Jeffrey's reply below it looks like it can end up in either file.

2010/1/20 Jeffrey Janner <Jeffrey.Janner@polydyne.com>:
> Thanks Konstantin.  That is where it was.
> Now I have something to document for the ops to run when the app hangs again.


Best regards,
Konstantin Kolinko

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


Mime
View raw message