[SM-981] Transaction Exception due to ServiceMix JMS Provider

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.1
• Fix Version/s: 3.2
• Component/s: servicemix-jms

Environment

All platforms. The bug was encountered on ServiceMix 3.1 running in JBoss against JBossMQ.

• Patch Info: Patch Available
• Assignee: Guillaume Nodet
• Reporter: Martin Landua
• Created: 26/Jun/07 07:43
• Updated: 27/Sep/07 14:29
• Resolved: 27/Sep/07 14:29

Description

Hi all,

under heavy load, we have encountered a problem when writing messages using the JMS provider in a synchronous, transactional flow.

The problem is that in the code (lines 100 and up)

producer.send(msg);
exchange.setStatus(ExchangeStatus.DONE);
channel.send(exchange);
} finally {
if (session != null)

{ session.close(); }
if (connection != null) { connection.close(); }
}

it is possible that the DONE state would return to the originator faster than the session and the connection is closed in the finally section. If this happens, the originator (and therefore owner of the transaction) will first commit and after this the provider would close the connection.

This results in a transaction exception.

From what we can tell, it should read like this:

producer.send(msg);
} finally {
if (session != null) { session.close(); }

if (connection != null)

{ connection.close(); }

}

exchange.setStatus(ExchangeStatus.DONE);
channel.send(exchange);

due to which we guarantee that the connection is safely closed before we send the confirmation back to the consumer.

All of our load tests succeeded after this change.

Best regards

Martin Landua