下面是我异常的截的一部份，
[5/2/12 11:11:11:546 CST] 0000000e ThreadMonitor W WSVR0605W: Thread "WebContainer : 55" (00000053) has been active for 654703 milliseconds and may be hung. There is/are 1 thread(s) in total in the server that may be hung.
[5/2/12 11:11:11:546 CST] 0000000e ThreadMonitor W WSVR0605W: Thread "WebContainer : 54" (00000052) has been active for 654531 milliseconds and may be hung. There is/are 2 thread(s) in total in the server that may be hung.
[5/2/12 11:11:11:546 CST] 0000000e ThreadMonitor W WSVR0605W: Thread "WebContainer : 18" (0000002c) has been active for 646390 milliseconds and may be hung. There is/are 3 thread(s) in total in the server that may be hung.
[5/2/12 11:11:11:546 CST] 0000000e ThreadMonitor W WSVR0605W: Thread "WebContainer : 20" (00000030) has been active for 651828 milliseconds and may be hung. There is/are 4 thread(s) in total in the server that may be hung.
[5/2/12 11:11:11:546 CST] 0000000e ThreadMonitor W WSVR0605W: Thread "WebContainer : 76" (00000068) has been active for 612484 milliseconds and may be hung. There is/are 5 thread(s) in total in the server that may be hung.
可以明显看出是线程池被沾满，但是我除了会看systemout.log,和systemerr.log文件，但是网上说看native_stderr.log和javacore.txt等文件，检查形成原因，但里面的内容我看不太懂，
求教大能们，教我一下如何检查这类问题的策略和技术方法，就算是代码有问题，我也想根据websphere相关日志文件找到根源在哪一块，但就是不知道怎么看，怎么找。请各位帮个忙。。
------解决方案--------------------
看java core文件中看看线程是不是有锁。也可以看看数据库有没有锁。结合systemOut.log前后的异常看看
------解决方案--------------------
同意三楼
你要知道怎么获得JavaCore文件，有kill -3 【进程号】的方法，javacore生产native_stdout.log文件中。
然后，要有一个工具去分析JavaCore里面有没有锁，被什么锁了。