[
https://issues.apache.org/jira/browse/AMQ-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13011807#comment-13011807
]
Timothy Bish commented on AMQ-3243:
-----------------------------------
Did you disable Message priority sorting on the client side? You can use
setMessagePrioritySupported(false) on the Connection or ConnectionFactory to do
that, or use the URI syntax. Disabling this will disable the basic message
priority sorting that the client consumer does.
If that doesn't help you might want to submit a test case that demonstrates the
issue you are seeing and shows what you expect.
> prioritizedMessages="false" does not disable message ordering of prioritized
> topic messages
> -------------------------------------------------------------------------------------------
>
> Key: AMQ-3243
> URL: https://issues.apache.org/jira/browse/AMQ-3243
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.4.2
> Environment: Operating System = Windows Vista version 6.0 running on
> x86
> Java; VM; Vendor = 1.6.0_23
> Runtime = Java HotSpot(TM) Client VM 19.0-b09
> Reporter: Robert Liguori
> Priority: Minor
>
> As per documentation
> (http://activemq.apache.org/per-destination-policies.html),
> I assumed the following would disable message ordering of topics, though it
> does not:
> <policyEntry topic=">" prioritizedMessages="false"
> producerFlowControl="true" memoryLimit="1mb">
> Notes: I've tested with Derby and KahaDB. I also make use of the
> MessageConsumer interface, instead of directly using TopicSubscriber.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
