"vickyk" wrote : | Should the above jsp work for the following CF definition ? | <tx-connection-factory> | | <jndi-name>TestJmsLocal</jndi-name> | | <rar-name>jms-ra.rar</rar-name> | | <connection-definition>org.jboss.resource.adapter.jms.JmsConnectionFactory</connection-definition> | | <config-property name="SessionDefaultType" type="java.lang.String">javax.jms.Topic</config-property> | | <config-property name="JmsProviderAdapterJNDI" type="java.lang.String">java:/TestJMSLocalProvider</config-property> | | <max-pool-size>20</max-pool-size> | | <application-managed-security/> | | </tx-connection-factory> | Only if TestJMSLocalProvider points at a plain ConnectionFactory, i.e. one that doesn't implement XAConnectionFactory. If the jms provider implements XA then don't use a local connection manager to manage transactions. You end up with the weaker Last Resource Gambit (i.e. the transaction observer pattern rather than the transaction participant pattern). But I'm just repeating what I've already said. I want a real use case not trying to support some broken/stupid configuration. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4142737#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...