WLS6.1 SP2 - Sorting JMS messages by priority fails to work

Question

          I have an app that uses a QueueSender to send messages of various priorities, 5
          and 9:
          queueSender.send(myMessage, DeliveryMode.PERSISTENT, myMessagePriority, Message.DEFAULT_TIME_TO_LIVE);
          I have configured a JMS Destination Key, JMSPriority(int, sort Descending), and
          bound it to the destination (from config.xml):
          <JMSServer Name="EJBTestServer" PagingStore="EJBTestStore"
          Store="EJBTestStore" Targets="fmlon66039server">
          <JMSQueue DestinationKeys="JMSPriority" JNDIName="EJBTestQueue"
          Name="EJBTestQueue" PriorityOverride="-1" StoreEnabled="default"/>
          </JMSServer>
          <JMSDestinationKey Direction="Descending" KeyType="Int"
          Name="JMSPriority" Property="JMSPriority"/>
          However the single MDB listening on the destination just gets the messages in
          the order they're sent: I would have expected all the priority 9 messages to come
          first.
          Note to simulate a long initialisation process, the MDB sleeps on receipt of the
          first message it receives; this gives the sender time to finish its sending.
          The sender sends one message per txn. The MDB receives one message per txn too.
          To prove my txns are 'good' my app logs the XID and the tx state whenever my app
          sends or receives a message.
          Any ideas anyone? Has anyone else got sorting by JMS priority to work in 6.1 SP2?
          simon.
          

Answer 1

I've submitted a doc enhancement request. Good idea.
          In general, doc changes are possible, but limited in older releases.
          Tom, BEA
          Simon Spruzen wrote:
          > Thanks, I didn't know about the pipe-line (can this be added to the documentation,
          > if you're still keeping 6.1 docs going? It might be also worth stressing in the
          > docs that even when sorting by priority (or anything else for that matter), it's
          > still only a hint that the server may choose to disregard in the interests of
          > timely message delivery. I 'knew' this, but my brain wasn't in gear.)
          >
          > You can probably guess how many messages my original test app was sending...
          >
          >
          > simon.
          >
          >
          > Tom Barnes <[email protected]> wrote:
          >
          >>There is a pipe-line of messages between the JMS server and the MDB.
          >>Messages get sorted on the JMS server but not within the pipe-line.
          >>The default size is 10. To reduce it, define a custom connection
          >>factory on the console for the MDB and modify the MDB descriptor
          >>to point to the custom connection factory's JNDI name.
          >>On the connection factory, reduce "MessagesMaximum"
          >>to 1 (the pipe-line size), and, for purposes of supporting
          >>WL MDBs properly, enable transactions, and set the acknowledge
          >>policy to "acknowledge-before".
          >>
          >>Tom, BEA
          >>
          >>Simon Spruzen wrote:
          >>
          >>>I have an app that uses a QueueSender to send messages of various priorities,
          >>
          >>5
          >>
          >>>and 9:
          >>>
          >>>queueSender.send(myMessage, DeliveryMode.PERSISTENT, myMessagePriority,
          >>
          >>Message.DEFAULT_TIME_TO_LIVE);
          >>
          >>>
          >>>I have configured a JMS Destination Key, JMSPriority(int, sort Descending),
          >>
          >>and
          >>
          >>>bound it to the destination (from config.xml):
          >>>
          >>>
          >>><JMSServer Name="EJBTestServer" PagingStore="EJBTestStore"
          >>> Store="EJBTestStore" Targets="fmlon66039server">
          >>> <JMSQueue DestinationKeys="JMSPriority" JNDIName="EJBTestQueue"
          >>> Name="EJBTestQueue" PriorityOverride="-1" StoreEnabled="default"/>
          >>></JMSServer>
          >>>
          >>>
          >>><JMSDestinationKey Direction="Descending" KeyType="Int"
          >>> Name="JMSPriority" Property="JMSPriority"/>
          >>>
          >>>
          >>>
          >>>
          >>>However the single MDB listening on the destination just gets the
          >>
          >>messages in
          >>
          >>>the order they're sent: I would have expected all the priority 9 messages
          >>
          >>to come
          >>
          >>>first.
          >>>
          >>>Note to simulate a long initialisation process, the MDB sleeps on receipt
          >>
          >>of the
          >>
          >>>first message it receives; this gives the sender time to finish its
          >>
          >>sending.
          >>
          >>>The sender sends one message per txn. The MDB receives one message
          >>
          >>per txn too.
          >>
          >>>To prove my txns are 'good' my app logs the XID and the tx state whenever
          >>
          >>my app
          >>
          >>>sends or receives a message.
          >>>
          >>>Any ideas anyone? Has anyone else got sorting by JMS priority to work
          >>
          >>in 6.1 SP2?
          >>
          >>>simon.
          >>
          >