To my knowledge, there is no way to read the message body from the management API. Typically the message body only needs to be read by the consumer itself. What specifically are you trying to accomplish?
I'm writing a debug application that allows for the replay of messages following a failed state and human intervention;
1->user raises order
2-> Order MBean fails 5 times, message moved to DLQ
3-> A Human at some stage in the future review the DLQ from my debugging app and makes the decision whether to replay; do a manual data fix, of purge the message - to do this they will review the message content (i.e. the body of the message that is a json representation of the order)
At the moment i can show them messages exist in the DLQ but not what is contained within them?
Any thoughts or suggested approach short of consuming the messages and rolling back the transactions :-) ?
Use a JMS queue browser?