Does anybody know of a way of mapping the light weight process id reported by a
tool such as prstat on Solaris on to something more meaningful e.g. is it a
session bean thread, tomcat thread, jboss system thread etc.
e.g. prstat output:
PID CPUPROCESS/LWPID
24187 12% java/
We are getting the following error:
[org.jboss.ejb.plugins.AbstractInstanceCache] Unable to passivate due to ctx
lock, id=X
This error starts happens after more than 1 day of normal activity where the
jboss process goes from using an average of 1% CPU usage to 90% CPU usage.
Is this becaus