EJB Call tracing not happening

14 views
Skip to first unread message

Sarbojeet Das

unread,
Oct 14, 2020, 3:05:38 AM10/14/20
to inspectIT
Hi team,

I have a middleware which support REST and EJB calls both . the agent is attached with the middleware pid.

I can see lot of REST API calls are being traced , but unable to see any EJB calls are being traced.

Please let us know if its supported and if yes, what is missing

below is the pid with jar attached:

arbor    12427 12334 16 Oct13 ?        02:36:07 /usr/java/jdk1.8.0_121/bin/java -D[Server:max05-fxjmw] -Xms1024m -Xmx4096m -server -XX:+UseG1GC -XX:+UseStringDeduplication -XX:MetaspaceSize=1024m -XX:MaxMetaspaceSize=2048m -Djava.util.logging.manager=org.jboss.logmanager.LogManager -Xbootclasspath/p:/home/arbor/EAP-7.1.0/modules/system/layers/base/org/jboss/logmanager/main/jboss-logmanager-2.0.7.Final-redhat-1.jar -Djgroups.bind_addr=max05-fxjmw -javaagent:/home/arbor/agent/inspectit-agent.jar -Dinspectit.repository=10.230.27.78:9070 -Dinspectit.agent.name=JMW -Djava.awt.headless=true -Djava.net.preferIPv4Stack=true -Djava.util.logging.manager=org.jboss.logmanager.LogManager -Djavax.net.ssl.trustStore=/home/arbor/EAP-7.1.0/domain/configuration/keystore/ssl_client.truststore -Djavax.net.ssl.trustStorePassword=2001hari -Djboss.bind.address=max05-fxjmw -Djboss.bind.address.management=max05-fxjmw -Djboss.domain.master.address=max05-fxjmw -Djboss.home.dir=/home/arbor/EAP-7.1.0 -Djboss.modules.system.pkgs=org.jboss.byteman,org.jboss.logmanager -Djboss.node.name=max05-fxjmw -Dorg.apache.coyote.http11.Http11Protocol.SERVER=JMW DC Server -Djboss.server.log.dir=/home/arbor/EAP-7.1.0/domain/servers/max05-fxjmw/log -Djboss.server.temp.dir=/home/arbor/EAP-7.1.0/domain/servers/max05-fxjmw/tmp -Djboss.server.data.dir=/home/arbor/EAP-7.1.0/domain/servers/max05-fxjmw/data -Dlogging.configuration=file:/home/arbor/EAP-7.1.0/domain/servers/max05-fxjmw/data/logging.properties -jar /home/arbor/EAP-7.1.0/jboss-modules.jar -mp /home/arbor/EAP-7.1.0/modules org.jboss.as.server



The application we are using is  JBoss EAP 7.1.6.GA (WildFly Core 3.0.21.Final-redhat-00001) 




Stefan Siegl

unread,
Oct 14, 2020, 5:19:08 AM10/14/20
to inspectIT
Hi,

You seem to be using the "old" inspectIT. In this you need to ensure that you have your invocation sequence tracer in place for EJB. You might want to check for that.

Best,
Stefan
Reply all
Reply to author
Forward
0 new messages