[TUSCANY-4018] JMS TransportServiceInterceptor using wrong values to set JMS headers in producer

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Java-SCA-2.x
• Fix Version/s: Java-SCA-2.x
• Component/s: Java SCA JMS Binding Extension
• Patch Info: Patch Available
• Assignee: Simon Laws
• Reporter: Jennifer Thompson
• Created: 20/Feb/12 22:32
• Updated: 21/Feb/12 11:32
• Resolved: 21/Feb/12 11:32

Description

In TransportServiceInterceptor.invokeResponse is setting the effective TimeToLive, Priority in the response message, but when the values are set in the producer, the values from the request are used, potentially leading to an incorrect value. So the following:

// Set jms header attributes in producer, not message.
int deliveryMode = requestJMSMsg.getJMSDeliveryMode();
producer.setDeliveryMode(deliveryMode);
int deliveryPriority = requestJMSMsg.getJMSPriority();
producer.setPriority(deliveryPriority);
long timeToLive = requestJMSMsg.getJMSExpiration();
producer.setTimeToLive(timeToLive);

Should be:

// Set jms header attributes in producer, not message.
producer.setDeliveryMode(responseJMSMsg.getJMSDeliveryMode());
producer.setPriority(responseJMSMsg.getJMSPriority());
producer.setTimeToLive(responseJMSMsg.getJMSExpiration());