Panasonic Youth rob sanheim writes about software, business, ruby, music, stuff and things



Posted
22 July 2005 @ 4pm

Tagged
Java

Discuss

You know your cache is slowing development when…

You see this in your logs:

[7/22/05 15:30:27:272 CDT] 10431043 ThreadMonitor W WSVR0605W: Thread "Servlet.Engine.Transports : 0" (35b135b1) has been active for 767,637 milliseconds and may be hung. There are 1 threads in total in the server that may be hung.
[7/22/05 15:33:34:094 CDT] 35b135b1 ThreadMonitor W WSVR0606W: Thread “Servlet.Engine.Transports : 0″ (35b135b1) was previously reported to be hung but has completed. It was active for approximately 954,459 milliseconds. There are 0 threads in total in the server that still may be hung.

(sigh)


2 Comments

Posted by
Ruud van Zundert
30 December 2005 @ 11am

Yeah, we’ve been seeing that too - do let us know when you’ve got a fix for this! ;-)


Posted by
Rob
30 December 2005 @ 12pm

Well our fix was to upgrade the database so the cache load went faster. =) If you mean actually removing Websphere’s warning message, well, I’m not sure if you would even want to do that if you could. Figure out where the hung (or slow) threads are, and fix them.


Leave a Comment

Web testing and validation Java technical interview guide - part 1