JMS Message Rollback Issue.

Question

Hi,
I have a requirement where i have to read from a queue and then insert into a table. There are 2 scenarios where the message should remain in the queue
a) If the insert fails
b) There is some exception after reading the message but before inserting into the table.
I am using Weblogic, Oracle and MQ Series
I have created the QCF (XA based) and also created a XAdatasource thru the WL console.
However, the XA does not seem to be happening!!
This is my spring configuration
<bean id="TxManager" class="org.springframework.transaction.jta.WebLogicJtaTransactionManager" >
<property name="jndiTemplate" ref="jndiTemplate"></property>
<property name="transactionManagerName" value="javax.transaction.TransactionManager"/>
</bean>
<!-- =================== ASPECT CONFIGURATION ===================== -->
<aop:config proxy-target-class="true">
<aop:advisor pointcut="execution(* *..*Processor*.*(..))" advice-ref="txReqAdvice"/>
<aop:advisor pointcut="execution(* *..*Listener*.*(..))" advice-ref="txReqAdvice" />
<aop:advisor pointcut="execution(* *..*Dao*.*(..))" advice-ref="txReqAdvice"/>
</aop:config>
<aop:config />
<tx:advice id="txReqAdvice" transaction-manager="TxManager">
<tx:attributes>
<tx:method name="save*" propagation="REQUIRED" timeout="100"/>
<tx:method name="on*" propagation="REQUIRES_NEW" timeout="100" />
<!-- <tx:method name="process*" propagation="REQUIRED" timeout="100"/>-->
</tx:attributes>
</tx:advice>
<tx:advice id="txReqNewAdvice" transaction-manager="TxManager">
<tx:attributes>
<tx:method name="create*" read-only="false" propagation="REQUIRES_NEW" />
<tx:method name="update*" read-only="false" propagation="REQUIRES_NEW"/>
<tx:method name="insert*" read-only="false" propagation="REQUIRES_NEW"/>
<tx:method name="add*" read-only="false" propagation="REQUIRES_NEW"/>
<tx:method name="*" propagation="REQUIRED"/>
</tx:attributes>
</tx:advice>
<!-- ====================================JTA End====================================== -->
<!-- JNDI Environment Template -->
<bean id="jndiTemplate"
class="org.springframework.jndi.JndiTemplate">
<property name="environment">
<props>
<prop key="java.naming.factory.initial">weblogic.jndi.WLInitialContextFactory</prop>
<prop key="java.naming.provider.url">t3://localhost:7001</prop>
</props>
</property>
</bean>
<!-- Start Connection Factory -->
<bean id="jmsQueueConnectionFactory"
class="org.springframework.jndi.JndiObjectFactoryBean">
<property name="jndiTemplate" ref="jndiTemplate">
</property>
<property name="jndiName" value="/jms/WLReceiverQCF">
</property>
<property name="lookupOnStartup" value="false"/>
<property name="proxyInterface" value="javax.jms.QueueConnectionFactory"/>
</bean>
<bean id="jmsXAQueueConnectionFactory"
class="org.springframework.jndi.JndiObjectFactoryBean">
<property name="jndiTemplate" ref="jndiTemplate">
</property>
<property name="jndiName" value="/jms/WLXAReceiverQCF">
</property>
<property name="lookupOnStartup" value="false"/>
<property name="proxyInterface" value="javax.jms.XAQueueConnectionFactory"/>
</bean>
<!-- End Connection Factory -->
<!-- Start Queue destination, queuetemplate, sender & Listener -->
<!-- Spring JMS Queue Connection Factory -->
<bean id="destinationQueue"
class="org.springframework.jndi.JndiObjectFactoryBean">
<property name="jndiTemplate">
<ref bean="jndiTemplate" />
</property>
<property name="jndiName">
<value>/jms/WLReceiverQueue</value>
</property>
<property name="proxyInterface" value="javax.jms.Queue"/>
</bean>
<bean id="jmsQueueTemplate"
class="org.springframework.jms.core.JmsTemplate102">
<property name="connectionFactory" ref="jmsQueueConnectionFactory">
</property>
<property name="defaultDestinationName" value="RequestQQ"/>
<!-- <ref bean="destinationQueue" />-->
<!-- </property>-->
<!-- <property name="defaultDestination" ref="destinationQueue"/>-->
</bean>
<bean id="jmsSender" class="com.sample.JmsSender">
<property name="jmsTemplate102">
<ref bean="jmsQueueTemplate"/>
</property>
</bean>
<bean id="jmsListener"
class="com.sample.JMSRequestListener" />
<bean id="jmsListenerContainer"
class="org.springframework.jms.listener.DefaultMessageListenerContainer">
<property name="connectionFactory" ref="jmsXAQueueConnectionFactory" />
<property name="destinationName" value="RequestQQ" />
<property name="messageListener" ref="jmsListener" />
<property name="transactionManager" ref="TxManager" />
<property name="transactionTimeout" value="100" />
<!-- <property name="sessionTransacted" value="true" />-->
</bean>
<bean id="datasource"
class="org.springframework.jndi.JndiObjectFactoryBean">
<property name="jndiTemplate" ref="jndiTemplate"/>
<property name="jndiName">
<value>jdbc/MyDS</value>
</property>
<property name="expectedType" value="javax.sql.DataSource"/>
<property name="lookupOnStartup" value="false"/>
</bean>
<bean id="hibernatePropsBean" class="org.springframework.beans.factory.config.PropertiesFactoryBean">
<property name="properties">
<props>
<prop key="hibernate.dialect">org.hibernate.dialect.OracleDialect</prop>
<prop key="hibernate.default_schema">common</prop>
<prop key="hibernate.show_sql">true</prop>
<prop key="hibernate.cache.provider_class">org.hibernate.cache.NoCacheProvider</prop>
<prop key="hibernate.connection.release_mode">after_transaction</prop>
</props>
</property>
</bean>
<bean id="sessionFactory" class="org.springframework.orm.hibernate3.LocalSessionFactoryBean">
<!-- <property name="useTransactionAwareDataSource" value="true"/>-->
<property name="dataSource" ref="datasource"/>
<property name="hibernateProperties" ref="hibernatePropsBean"/>
<property name="mappingResources">
<list>
<value>com/sample/Event.hbm.xml</value>
</list>
</property>
</bean>
<bean id="EventDAO" class="com.sample.EventSpringDao">
<property name="sessionFactory" ref="sessionFactory"/>
</bean>
</beans>
Can somebody point me where i am doing a mistake?
Regards
Siva.

Answer 1

Ensure that the custom connection factory with JNDI name "/jms/WLXAReceiverQCF" is configured with "XA Transactions Enabled".
Try setting the Spring "sessionTransacted" to "false" -- which should be the default. googling "Spring sessionTransacted" reveals there's a bit of weirdness with this field, and behavior may differ with different JMS vendors.
FWIW For a variety of reasons, including your plans to use MQSeries XA, I would normally recommend using WebLogic MDBs rather than the Spring messaging container.
Tom