[
https://issues.apache.org/activemq/browse/AMQ-1957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46157#action_46157
]
Gary Tully commented on AMQ-1957:
---------------------------------
Alexis,
there are some neat changes, by any chance do you have a relevant pure JMS test
case that will protect them?
> All in one patch concerning message dispatching problems with Spring DMLC
> 2.5.5 +JBoss 4.2.2 with cacheLevel=CACHE_NONE
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-1957
> URL: https://issues.apache.org/activemq/browse/AMQ-1957
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.0.0, 5.1.0, 5.2.0
> Environment: Spring DMLC 2.5.5, JBoss 4.2.2, JDK 5 / 6, ActiveMQ
> 5.0.0.19 as remote broker with TCP transport
> Reporter: Alexis Kinsella
> Attachments: IndirectMessageReference.java.patch,
> PrefetchSubscription.java.patch, Queue.java.patch
>
>
> Here is an all in one patches applied on version 5.0.0.19
> It is composed from 4 files directly applicable on Fuse v5.0.0.19
> They all concern package 'org.apache.activemq.broker.region'.
> The effects of this patch are the following:
> * Avoid multiple dispatching of same message to multiple subscription
> multiple time (Multiple dispatch to client consumers in some cases = > causes
> multiple commits for same message => causing negatives counters on Pending
> Message Count)
> * Avoid the broker hanging when a queue has numerous messages in one queue
> * MB-386 + Correction
> * Some other little glitches
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.