|
When the one thread takes 100% of the CPU I think your best bet, as Frances suggests, is to use STRSST D/A/D to dump the offending thread, dump it to print (spool). Take several dumps during this period in order to produce evidence of what code is executing at the time. What do the stacks look like? Further, once you've identified the offending thread #, use SST to dump it even when it isnt causing the problem at the time. The idea is to at least identify what kind of thread it is such as servlet thread, gc thread, orb/ejb thread, etc.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.