We are seeing an issue where JBM messages are getting 'lost' until the server is restarted. This is in a cluster of two JBM servers running on JBEAP 4.3 GA. The messages appear in the database, but both partial queues report 0 messages. When the servers are restarted, they find the messages and process them successfully. The messages in the database are not associated with any transaction or consumer. The root cause of this may be due to problems connecting to the database, as we see some ORA-17008 errors for a few minutes at the same time as these messages were processed. (JBM seems to assume that its a deadlock, and retry 25 times). Once the ORA errors go away, JBoss messaging continues as normal for any new messages, although the ones that were being processed get forgotten about. How does JBM cope with the database becoming unavailable during a transaction? Especially between PREPARE and COMMIT on an XA transaction. Could this cause messages to get stuck in the database? It is worth adding that the database is Oracle RAC, but that the logs indicate that the database was fine, and that no failover occurred, so it was likely a networking issue, but its not good that the messages got lost until we restarted the servers. Matt View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4194256#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...