[jboss-cvs] JBoss Messaging SVN: r8344 - branches/JBMESSAGING_1879/src/main/org/jboss/messaging/core/impl.

[jboss-cvs-commits at lists.jboss.org]

Author: gaohoward
Date: 2011-06-15 23:43:01 -0400 (Wed, 15 Jun 2011)
New Revision: 8344

Modified:
   branches/JBMESSAGING_1879/src/main/org/jboss/messaging/core/impl/JDBCPersistenceManager.java
Log:
comments


Modified: branches/JBMESSAGING_1879/src/main/org/jboss/messaging/core/impl/JDBCPersistenceManager.java
===================================================================
--- branches/JBMESSAGING_1879/src/main/org/jboss/messaging/core/impl/JDBCPersistenceManager.java	2011-06-15 16:14:28 UTC (rev 8343)
+++ branches/JBMESSAGING_1879/src/main/org/jboss/messaging/core/impl/JDBCPersistenceManager.java	2011-06-16 03:43:01 UTC (rev 8344)
@@ -1742,10 +1742,12 @@
                         //2. message claimed and re-sucked, but the first suck get in between the second suck
                         //having updated to 'S' state and doing this update, giving the first suck a 
                         //chance to successfully update it, then the resucked one get here-- this results in
-                        //duplicated messages!!!!
+                        //duplicated messages!!!! This case only happens in using multiple consumers on a 
+                        //distributed queue case!
                         //to solve this we need a suckerLock object to serialize the update and a counter
                         //if counter > 1 and we get here, that's fine
                         //if counter = 1 and we get there, throw exception!
+                        //JBMESSAGING-1879
                         if (counter == 1)
                         {
                            throw new JMSException("Failed to move message " + ref.getMessage().getMessageID() + ", already sucked.");