[SWS-383] JmsSenderConnection does not correlate response messages on permanent response queues Created: 19/Jun/08  Updated: 21/Jul/08  Resolved: 19/Jun/08

Status: Closed
Project: Spring Web Services
Component/s: Core
Affects Version/s: 1.5, 1.5.1, 1.5.2
Fix Version/s: 1.5.3

Type: Improvement Priority: Major
Reporter: Arjen Poutsma Assignee: Arjen Poutsma
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


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."

Comment by Arjen Poutsma [ 21/Jul/08 ]

Closing issues in 1.5.3

Generated at Sat Oct 20 02:55:38 UTC 2018 using JIRA 7.9.2#79002-sha1:3bb15b68ecd99a30eb364c4c1a393359bcad6278.