AppD Archive

Missing EJB-Calls in BusinessTransactions

CommunityUser
Splunk Employee
Splunk Employee

Hello,

i have deployed following example from JBoss on my JBoss-EAP:

https://github.com/jboss-developer/jboss-eap-quickstarts/tree/6.4.x-develop/ejb-in-ear

The deployment works fine, but i can't see the ejb-calls from this application.

image.png

image.png

Mayby this is a configuration-problem. My gwt-application shows the ejb-call.

The logfile of the agent seems to be allright without errors.

Please tell me if you need more information.

Thank you for your help.

Regards

    Sascha

0 Karma
1 Solution

CommunityUser
Splunk Employee
Splunk Employee

Hi Arun,

you are right. The Transaction was quicker than 10ms. After implementing a "wait" for about 1 second, the ejb-call is shown in the call-graph.

Thank you for your help.

Regards

    Sascha

View solution in original post

0 Karma

Arun_Dasetty
Super Champion

Hi Sascha,

There are two reason for EJB BTs missing under "Business transaction" screen:

- By default EJB business transaction auto discovery is disabled under Configure -> Instrumentation->  "Transaction Detection" screen

- Other reson though EJB Auto discovery enabled under Transaction detection screen is, Say you have Servlet BT discovered under "Business transactions" list which is expected to call the EJB than agent considers EJB is nested call to parent BT servlet in this case so EJB will not not be discovered in BT list but should be shown in snapshot "Call graph" again if EJB api calls in servlet snaphot is NOT taken more than 10 ms you might not see as well Or if it is partial snapshot, say in reference to your second screenshot if your servlet calls EJB api check whether the ejb sub call is taken considerable time

Are you mean EJB is shown up on POJO/GWT BT rules snapshot call graph section in UI? if this is the case as said above it wil not discover as separete BT as expected

You can disable or exclude parent BT discovered and define custom ejb rule under Configure -> Instrumentation->  "Transaction Detection" screen and see if that changes helps here.

Regards,

Arun

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Hi Arun,

you are right. The Transaction was quicker than 10ms. After implementing a "wait" for about 1 second, the ejb-call is shown in the call-graph.

Thank you for your help.

Regards

    Sascha

0 Karma
Get Updates on the Splunk Community!

Fueling your curiosity with new Splunk ILT and eLearning courses

At Splunk Education, we’re driven by curiosity—both ours and yours! That’s why we’re committed to delivering ...

Splunk AI Assistant for SPL 1.1.0 | Now Personalized to Your Environment for Greater ...

Splunk AI Assistant for SPL has transformed how users interact with Splunk, making it easier than ever to ...

Unleash Unified Security and Observability with Splunk Cloud Platform

     Now Available on Microsoft AzureOn Demand Now Step boldly into the AI revolution with enhanced security ...