Hi,
This happens when the transaction manager tries to enlist the
Informix XA resource into a transaction that the JMS XA
resource is already enlisted with.
Looks like the problem is that the Informix XA driver thinks
that all XA resources are Informix XA resources.
That is a nice way to create
Using a JMS Queue and a Message Driven Bean that is using a JDBC
DataSource I get the following exeception.
I am using the InformixXA JDBC Driver. This works without the XA driver
but I get a semantic warning.
java.lang.ClassCastException: org.jboss.mq.SpyXAResource
at
com
