Short answer: you can't. Journal-based persistence is the only option currently. This has been discussed on the forum a few times in the past.
Thanks for the response.
I was thinking of pulling the messages from the DLQ database like in previous versions of JBoss hornet. Since there is no database now can a mdb tell the DLQ to resend a specific message like a mdb can listen to the DLQ.
I'm not sure I understand your use-case. Can you elaborate on exactly what you're trying to do?
My client currently uses oracle to handle their queues and they have an error queue.
Since the Qracle JMS is persisted in an Oracle database the client can have Oracle resend a message from the error queue to the original destination.
However not all the messages that end up in the error queue will need to be resent to the original destination.
In the JBoss case the dead letter queue would replace the Oracle error queue.
Some but not all of the messages in the dead letter queue would need to be resent to the original destination.
just implement an MDB that consumes from the DLQ and writes to the database