Uploaded image for project: 'Spring Web Services'
  1. Spring Web Services
  2. SWS-383

JmsSenderConnection does not correlate response messages on permanent response queues

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.5, 1.5.1, 1.5.2
    • Fix Version/s: 1.5.3
    • Component/s: Core
    • Labels:
      None

      Description

      When using a permanent response queue, the client-side JMS transport currently selects the first available messages on said queue. This is undesired behavior.

      Instead, we should use a message selector to receive responses which have a correlation id that is equal to the request message. This is only required for permanent queues; temporary queues don't have this problem.

      See http://forum.springframework.org/showthread.php?p=187209 and http://mail-archives.apache.org/mod_mbox/ws-axis-dev/200701.mbox/raw/%[email protected]ss.com%3E/3#rr-requester-request, stating

      "A correlated response message is one where the value of the JMSCorrelationID header field is the same as the value of the JMSMessageID of the request message."

        Activity

          People

          • Assignee:
            arjen.poutsma Arjen Poutsma
            Reporter:
            arjen.poutsma Arjen Poutsma
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: