This is about the basic scenarios, so, for example, not supporting a pattern of writing a message to a queue and waiting for a response message on a different queue.
Furthermore, this issue only concerns Java agent support for the JMS API, we need to see how things get presented in the UI for real async delayed message handling.
A basic requirement is context propagation, and transaction creation when reading from queue.
Nice-to-have - span of the publishing event with details like queue name.