[
http://jira.jboss.com/jira/browse/JBMESSAGING-1073?page=comments#action_1... ]
Tim Fox commented on JBMESSAGING-1073:
--------------------------------------
Sorry to be a pain, but that is the procedure.
Quite often issues turn out to be already reported in JIRA, or already fixed in later
versions so we don't need to add a JIRA report
We need to go through the triage process to ascertain whether we need to add a new JIRA
report.
JMS messages are not taken from the queue after database connection
recovery
----------------------------------------------------------------------------
Key: JBMESSAGING-1073
URL:
http://jira.jboss.com/jira/browse/JBMESSAGING-1073
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.3.0.GA
Environment: JBoss.4.2.1 JBossMessaging 1.3GA Oracle 10g database jdk 1.5 on
solaris intel
Reporter: Evgueni Smoliar
Assigned To: Tim Fox
We have 2 jboss server running in the cluster. Messaging is also configured with
clustered queues.
At one moment we had a database crash. Database was recovered in 5 minutes and
connections from jboss were reestablished . All applications works OK, new messages
processed correctly. The problem is with the messages processed during the crash time. JMS
could not commit them and couldn't rollback at the time. After reestablishing of the
connection this messages are not redelivered anymore.
The only way to get those message delivered is to restart jboss servers.
This is strange problem which we never experienced with old jboss-jms implementation.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira