You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Marnie McCormack (JIRA)" <qp...@incubator.apache.org> on 2007/04/19 15:14:15 UTC
[jira] Updated: (QPID-26) Provide prority parameter implementation
for message MessageProducer.send method
[ https://issues.apache.org/jira/browse/QPID-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marnie McCormack updated QPID-26:
---------------------------------
Fix Version/s: (was: M2)
M3
Moving unresolved JIRAs from M2 to M3, in preparation for M2 release
> Provide prority parameter implementation for message MessageProducer.send method
> --------------------------------------------------------------------------------
>
> Key: QPID-26
> URL: https://issues.apache.org/jira/browse/QPID-26
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker, Java Client
> Reporter: Marnie McCormack
> Assigned To: Robert Greig
> Fix For: M3
>
>
> The priority parameter on the javax.jmx.MessageProducer.send method is exposed in the qpid implementation (org.apache.qpid.client.BasicMessageProducer). However, it doesn't actually have any impact under the covers i.e. it is currently ignored and has no effect. Thus we do not provide any way to expedite messages using the priority field.
> This is clearly less than optimal and needs to be addressed. The setting the priority flag on the send method should set the JMSPriority field in the header. The information below is taken from the JMS specification (see spec for refs/more detail):
> The JMSPriority header field contains the message's priority. When a message is sent, this field is ignored. After completion of the send, it
> holds the value specified by the method sending the message. JMS defines a ten-level priority value, with 0 as the lowest priority and 9 as the
> highest. In addition, clients should consider priorities 0-4 as gradations of normal priority and priorities 5-9 as gradations of expedited priority.
> JMS does not require that a provider strictly implement priority ordering of messages; however, it should do its best to deliver expedited messages ahead of normal messages.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.