EJB Sensor dynaTrace 6.1
Hi,
We've recently upgraded to DT 6.1 and are having issues instrumenting one of our applications. Our application has EJBs and we have the EJB sensor placed. We defined some custom sensors on on EJB beans. What we are seeing is that the EJB beans are being captured by auto sensors and not the custom sensors we have placed.
Is there any difference in 6.1 how EJB beans are captured?
Thanks,
Antoine
Hi.
There is no difference. If you have your custom sensors defined make sure that
a) these methods are really loaded and called. I always start by looking at the "Deployed Sensors" tab in the Agent Overview Dashlet. It shows all the sensors that have really been placed. Try to find the method that you think you have instrumented. It should show up there. If it does not you either made a mistake in your sensor configuration or the class has not been loaded yet
b) that your custom sensors have a higher priority then the EJB Sensor. You can change the priority by moving your sensor group higher up than the EJB SEnsor in the SEnsor Placement Settings in your System Profile
Andi
Hi Andreas,
I've checked the agents overview and I do see that the EJB bean is deployed on the particular sensor. I've also ensured that our custom sensor group has a higher priority than EJB Invocation. But the EJB beans are still being captured by auto sensors.
Is there any difference in the type of license used, we're testing the potential taxation of DT, so we're using a production license?
Thanks,
Antoine
There is no difference in licensing. One additonal thought. there are a lot of methods that look alike yet are different in e.g.: number of arguments or visiblity (public, protected, ...). Make sure that your custom sensor is really capturing the method you have intended. Use the Class Browser to select the method which will make sure it contains the correct list of arguments as well as the correct visiblity level
If that still doesnt solve your problem I suggest you open up a support ticket
Andi
