Ordering Group doesn't work with DUPS_OK_ACKNOWLEDGE and default ConnectionFactory ---------------------------------------------------------------------------------- Key: JBMESSAGING-1779 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1779 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.4.0.SP3.CP09 Reporter: Takayoshi Kimura Fix For: 1.4.0.SP3.CP10 Attachments: test379563.bsh A JMS client which uses DUPS_OK_ACKNOWLEDGE acknowledge mode cannot receive more than 1 message with Ordering Group. Because with DUPS_OK_ACKNOWLEDGE, JBM doesn't send an ack for each message but bundles acks. Ordering Group requires an ack for each message, so this combo basically doesn't work. This is not the case when disable batch ack by setting ConnectionFactory.DupsOKBatchSize=1. Looks like a bug or an implementation limitation. According to the document, the AUTO_ACKNOWLEDGE and DUPS_OK_ACKNOWLEDGE work in the same manner: http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/4.... > For AUTO_ACKNOWLEDGE and DUPS_OK_ACKNOWLEDGE modes, the completion of the message is identified by either > - successful returning from the MessageConsumer.receive() methods > - successful returning from the onMessage() call of the MessageListener()

Ordering Group doesn't work with DUPS_OK_ACKNOWLEDGE and default ConnectionFactory ---------------------------------------------------------------------------------- Key: JBMESSAGING-1779 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1779 Project: JBoss Messaging Issue Type: Bug Components: Documentation and Training Affects Versions: 1.4.0.SP3.CP09 Reporter: Takayoshi Kimura Fix For: 1.4.0.SP3.CP10 Attachments: test379563.bsh A JMS client which uses DUPS_OK_ACKNOWLEDGE acknowledge mode cannot receive more than 1 message with Ordering Group. Because with DUPS_OK_ACKNOWLEDGE, JBM doesn't send an ack for each message but bundles acks. Ordering Group requires an ack for each message, so this combo basically doesn't work. This is not the case when disable batch ack by setting ConnectionFactory.DupsOKBatchSize=1. Looks like a bug or an implementation limitation. According to the document, the AUTO_ACKNOWLEDGE and DUPS_OK_ACKNOWLEDGE work in the same manner: http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/4.... > For AUTO_ACKNOWLEDGE and DUPS_OK_ACKNOWLEDGE modes, the completion of the message is identified by either > - successful returning from the MessageConsumer.receive() methods > - successful returning from the onMessage() call of the MessageListener()

Ordering Group doesn't work with DUPS_OK_ACKNOWLEDGE and default ConnectionFactory ---------------------------------------------------------------------------------- Key: JBMESSAGING-1779 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1779 Project: JBoss Messaging Issue Type: Bug Components: Documentation and Training Affects Versions: 1.4.0.SP3.CP09, 1.4.5.GA, 1.4.6.GA Reporter: Takayoshi Kimura Assignee: Howard Gao Fix For: 1.4.0.SP3.CP10, 1.4.6.GA.SP1, 1.4.7.GA Attachments: test379563.bsh A JMS client which uses DUPS_OK_ACKNOWLEDGE acknowledge mode cannot receive more than 1 message with Ordering Group. Because with DUPS_OK_ACKNOWLEDGE, JBM doesn't send an ack for each message but bundles acks. Ordering Group requires an ack for each message, so this combo basically doesn't work. This is not the case when disable batch ack by setting ConnectionFactory.DupsOKBatchSize=1. Looks like a bug or an implementation limitation. According to the document, the AUTO_ACKNOWLEDGE and DUPS_OK_ACKNOWLEDGE work in the same manner: http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/4.... > For AUTO_ACKNOWLEDGE and DUPS_OK_ACKNOWLEDGE modes, the completion of the message is identified by either > - successful returning from the MessageConsumer.receive() methods > - successful returning from the onMessage() call of the MessageListener()