DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.
| Info |
|---|
This page applies to Java Broker versions before 0.18. For the master copy of this documentation see the Other Queue Types section in the Java documentation |
General Information
The Qpid 0.7 release introduces Last Value Queues (LVQs) into the Java Messaging Broker. The LVQ implementation in the Java Broker provides a superset of the behaviour of the LVQ in the C++ Broker. It is hoped that later revisions of the C++ Broker will adopt the same enhanced semantics.
...
Setting the Qpid pre-fetch to 1 for your client means that message priority conflation will be honoured by the Qpid broker as it dispatches messages to your client. A default for all client connections can be set via a system property:
...
There is a slight performance cost here if using the receive() method and you could test with a slightly higher pre-fetch (up to 10) if the trade-off between throughput and prioritisation conflation is weighted towards the former for your application. (If you're using OnMessage() then this is not a concern.)
...
If you are using the receive() method to consume messages then you should also only use one consumer per session with priority queues. If you're using onMessage() then this is not a concern.
...