PostgreSQL does not support two phase commit, see the FAQ for more information.
Thanks for replying.
Actually i don't require JMS to support transaction. But I need OTHER connection management features SUCH AS CONNECTION POOLING.
in the jms-ds.xml file, there are following codes:
< jndi-name>JmsXA< /jndi-name>
< xa-transaction/ >
< adapter-display-name>JMS Adapter< /adapter-display-name>
< config-property name="SessionDefaultType" type="java.lang.String">javax.jms.Topic< /config-property>
< security-domain-and-application>JmsXARealm< /security-domain-and-application>
If i just remove the "< xa-transaction/ >", does this mean the connection is still managed properly and without transaction feature.
Or I just need to set the JNDI in jboss.xml file to be one of value set in the uil2-service.xml file? (I mean there is no need to use jms-ds.xml file).
I try to modify my jboss.xml file so that it includes :
< resource-ref >
< res-ref-name>jms/LocalQueueConnectionFactory< /res-ref-name>
< jndi-name>java:/ConnectionFactory< /jndi-name>
I try to use jndi-name here instead of using resource-name.
But the jms client running in another JVM cannot receive the message in the jboss queue.
Which Invokation Layer are you using? AFAIK the default in JBoss 3.2.3 is the JVM IL, which is the fastest but requires the JMS client and server to run in the same JVM.
IF (!!!) I remember correctly, when we were trying out the different ILs, we changed the QueueFactoryRef and TopicFactoryRef attributes of the JMSProviderLoader MBean config in:
The different Invokation Layers are defined in: