search

stagemonitor / stagemonitor-mailinglist

GitHub issues abused as a mailing list
3 stars 0 forks source link

Call Tree Always Empty on Tomcat #73

Open motobeats opened 6 years ago

motobeats commented 6 years ago

I'm experiencing the call tree always empty issue on Tomcat 7 with JRE 7. Only using the brower widget currently.

I read through #41 and #44 but none of those changes helped.

Current JAVA_OPTS - I know instrumenting "java" classes would never be done but at this early stage I am only trying to get a call tree to populate. I added a sleep timer (Thread.sleep) to a very simple JSP just as a way to have something long running for stagemonitor to grab. /usr/lib/jvm/java/bin/java -server -Xms2048m -Xmx2048m -XX:MaxPermSize=512m -XX:PermSize=512m -javaagent:/var/lib/tomcat7/webapps/stagemonitor/WEB-INF/lib/byte-buddy-agent-1.7.9.jar -DSTAGEMONITOR_INSTRUMENT_INCLUDE=java

Included Stagemonitor by downloading the dependancies and including the jars in WEB-INF/lib. With that I got the widget to appear plus the signature and JVM metrics, all without using byte-buddy-agent. Adding the javaagent later has not added anything.

Also tried setting the Min Execution Time absurdly low to no avail. However, I'm not sure this setting is actually getting changed.

No mention of Stagemonitor, specifically the healthchecks, in catalina.log or tomcat.log which has me suspicious.

Java Version

java version "1.7.0_161"
Java(TM) SE Runtime Environment (build 1.7.0_161-b13)
Java HotSpot(TM) 64-Bit Server VM (build 24.161-b13, mixed mode)

Stagemonitor Version ./gradlew copyLibs -PstagemonitorVersion=0.88.4

Regards,

Andrew

motobeats commented 6 years ago

Updated to Java 8 but same result

java version "1.8.0_151" Java(TM) SE Runtime Environment (build 1.8.0_151-b12) Java HotSpot(TM) 64-Bit Server VM (build 25.151-b12, mixed mode)