TXOP="D" means the transaction was prepared but not committed.
Besides that, EJB3 questions are answered in the EJB3 forum.
ConfigJBossMDB is useless for EJB3 its a whole different implementation.
Nag the EJB3 developers to create a ConfigJBossMDBEJB3 like I've been
trying to do for a while now. ;-)
You probably also want to configure this:
http://jira.jboss.com/jira/browse/JBAS-1341 + related links
since it isn't enabled by default
(it is still considered "experimental" - i.e. not enough users have tried it out yet - no bugs have been reported with it, yet.... :-).
Thanks for your reply, I attempted to get the suggested XARecovery configuration operational. I did run into an error. Admittedly I'm new to reading the Jira but as I read it; the patch should be included in my version of the Application Server 4.2.1 and all that I should have to do is the configuration entries in jboss-4.2.1.GA/server/default/deploy/jms/mysql-jdbc2-service.xml
org.jboss.mq.SpyJMSException: Could not restore messages to destination : QUEUE.xefex-eventQueue; - nested throwable: (java.sql.SQLException: Column Index out of range, 3 > 1. )
Caused by: java.sql.SQLException: Column Index out of range, 3 > 1.
I've downloaded the JBoss AS source and I think the problem resides in line 620 of org.jboss.mq.pm.jdbc2.PersistenceManager
stmt = c.prepareStatement(SELECT_MESSAGE_KEYS_IN_DEST);
stmt = c.prepareStatement(selectMessagesInDest);
In the file jboss-4.2.1.GA/server/default/deploy/jms/mysql-jdbc2-service.xml alter the line for the entry SELECT_MESSAGE_KEYS_IN_DEST to SELECT_MESSAGE_KEYS_IN_DEST = SELECT MESSAGEID, MESSAGEBLOB, TXID, TXOP FROM JMS_MESSAGES WHERE DESTINATION=?
This should work in both the XA and non XA configuration as the columns are additive. Unfortunately after the fix XA recovery appears to be operational but it didn't solve my original problem. I'll bug the EJB3 guys to see if they can direct me into proper configuration for JBossMQ persistence with EJB3