My Java application (a standalone server) consumes 80% CPU right upon
startup for no apparent reason. If I do a kill -QUIT on the process
all the Java threads are idle. The app uses native JNI libraries
including oracle OCI driver. So given that there is no activity in the
JVM something must be happening in the native code and I want to do
find out what that is.
What is the best way to peek into the state of the JVM in terms of OS
threads? I would like the OS equivalent of the JVM threaddump - the
core file. If I do gcore on the process I cannot look at it in gdb
because the java executable itself is compiled without the symbolic
information. What is the way to go about it on Solaris?
Thanks,
- Robert
startup for no apparent reason. If I do a kill -QUIT on the process
all the Java threads are idle. The app uses native JNI libraries
including oracle OCI driver. So given that there is no activity in the
JVM something must be happening in the native code and I want to do
find out what that is.
What is the best way to peek into the state of the JVM in terms of OS
threads? I would like the OS equivalent of the JVM threaddump - the
core file. If I do gcore on the process I cannot look at it in gdb
because the java executable itself is compiled without the symbolic
information. What is the way to go about it on Solaris?
Thanks,
- Robert