cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nan Xu (JIRA)" <>
Subject [jira] [Created] (CXF-5293) XA transaction for soap over jms not fully working
Date Sat, 21 Sep 2013 04:14:51 GMT
Nan Xu created CXF-5293:

             Summary: XA transaction for soap over jms not fully working
                 Key: CXF-5293
             Project: CXF
          Issue Type: Bug
          Components: Configuration, Integration, Transports
    Affects Versions: 2.7.6
         Environment: weblogic 11g with cxf 2.7.6 and spring 3.2.0
            Reporter: Nan Xu

trying to achieve such a scenario.
1. soap message was sent to a inbound queue.
2. cxf pick up the soap message from inbound queue, then process it(do a database update)
3. response message send to outbound queue.

expected behavior:
when the outbound message can not be sent. the database change rollback, and inbound message
was send back to the dead letter queue, which is configured at inbound queue failed delivery
setting.(based on redelivery time)

cxf configuration.

    <bean id="dbService" class="com.test.DBActionImpl"/>    <!--update DB-->
     <jaxws:endpoint id="dbServiceEndPoint" implementor="#dbService" address="jms://">
			<bean class="org.apache.cxf.transport.jms.JMSConfigFeature" p:jmsConfig-ref="jmsConfig"
 	<bean id="jmsConfig" class="org.apache.cxf.transport.jms.JMSConfiguration"

        <bean id="jmsDestinationResolver" class=""

all the db datasource, jms connection factory and transaction manager are XA.
I pause the outbound queue production in weblogic to generate the outbound message sending

No message was send to Dead Letter Queue and DB change get committed.

tried with a standard spring jms listener in this way.

public class MyMessageListener implements MessageListener {
	private DBAction dbAction;
	private ResponseSender responseSender;  //jms sender use jmsTemplate

	public void onMessage(Message message) {
		if (message instanceof TextMessage) {
			try {
				System.out.println("I get message:  "+ ((TextMessage) message).getText());
			} catch (JMSException ex) {
				throw new RuntimeException(ex);
		} else {
			throw new IllegalArgumentException("Message must be of type TextMessage");

everything works fine. means when outbound queue production paused, the message was send to
dead letter queue and db change reverted.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message