I knew that DT system can recognize the Asynchronous invocation calls. And the purepath tree will record it as asyn call. But is there any way to drill down what happened in this "asynchronous invocation calls"? Of cause the both server installed agent now.
all details are show in the pure path, for example, if you put a custom sensor in a method behind the receive() you will see that method in the pure path.
Dynatrace correlates the async call in one unique, end to end, pure path with all details.
Na (& Josep),
JMS is a special case that sometimes requires an extra bit of work to see the processing after the receive call. The custom sensor that's required is documented here:
Note that the custom sensor is added to the JMS Receive Entry Point sensor pack which is defined at the server level. In this case, you don't add the custom sensor(s) to a sensor pack in the system profile.