Stephen,
Could you please describe the following details? The mule-descriptors having your jdbc endpoints, where were jdbc ones configured (inbound/outbound), what transaction attributes?
Andrew
On 3/7/07, Stephen Magee <Stephen_Magee@...> wrote:
Andrew,
Due to current pressures I won't
have a chance to put up an example config until next week, but in the mean
time:
We have a UMO that takes a message of an
ActiveMQ queue, updates a database and then publishes to another ActiveMQ queue
all within a XA transaction (note that the queues are on separate brokers).
Without the changes that we have made we
got a lot of XA errors and on stepping through the code noticed that the
database was updated as soon as the insert/update was executed (i.e. before the
message had been forwarded to the outbound queue).
We have had no problems with another part
of the system that bridges the two remote ActiveMQ brokers in a XA transaction
i.e. we only encountered the problem when a JDBC connection was involved.
We're using Mule 1.3.2 with ActiveMQ,
Oracle 10g and the Oracle JDBC driver. Mule is running standalone and using
JOTM as the transaction manager.
Stephen
