It seems like you are correct. the JMS transactions behind our MDB causes the @Traced(type="MDB") to just use the existing span from the JMS transaction.
So when looking in APM in the list of types, the type named MDB is empty of any transactions.
I also tried with @Traced in another part of the code where we have a incomingWebRequest starting the transaction and we run into the same "issue" there where the type parameter is ignored.
It feels like it is difficult to instrument a java application with APM this way. Is there any document "best practice" for this out there?
Regards,
Fredrik