APM data not coming in KIbana for Jboss EAP running on Wildfly using EJB instead of HTTP

If you are asking about a problem you are experiencing, please use the following template, as it will help us help you. If you have a different problem, please delete all of this text :slight_smile:

TIP 1: select at least one tag that further categorizes your topic. For example server for APM Server related questions, java for questions regarding the Elastic APM Java agent, or ui for questions about the APM App within Kibana.

TIP 2: Check out the troubleshooting guide first. Not only will it help you to resolve common problems faster but it also explains in more detail which information we need before we can properly help you.

Kibana version: 7.9.2

Elasticsearch version: 7.9.2

APM Server version: 7.9.2

APM Agent language and version:1.18.0

Browser version: Chrome

Original install method (e.g. download page, yum, deb, from source, etc.) and version: RPM

Fresh install or upgraded from other version? Fresh

Is there anything special in your setup? For example, are you using the Logstash or Kafka outputs? Are you using a load balancer in front of the APM Servers? Have you changed index pattern, generated custom templates, changed agent configuration etc. None

Description of the problem including expected versus actual behavior. Please include screenshots (if relevant):

We have deployed APM Agent on our Jboss EAP 7.1.0 running on Wildfly and using EJB on backend. We checked supported technologies and I guess Jboss EAP is supported in APM to get transactional data. However I am not sure of internal mechanism, how APM works. Does APM only works for REST services or it also support EJB ?

Below is the configuration we are using and JVM data is being displayed in Kibana. Regarding Error logs.. Nothing in APM server logs nor anything in Application Logs. Please suggest why Transactional data is not getting generated.

Java Version
java version "1.8.0_121"
Java(TM) SE Runtime Environment (build 1.8.0_121-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode)

Configuration Done

There is no dedicated support for EJB. Historically, remote invocations of EJBs would rely on RMI (or CORBA, or proprietary protocol in some maybe), which wouldn't be supported OOTB. The exception may be message beans, which implement the JMS MessageListener IIRC, or if there is some way of making remote EJB invocations through SOAP (I am not aware of such).

So, normally, EJB invocations are not expected to be automatically traced. You can use our public API to achieve that.

Other than that, as long as you are using a supported JBoss version (which is the case)- Servlet-based transactions should be captured and reported. If that doesn't work, check agent logs for hints.

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.