• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

XA vs non-XA

 
Greenhorn
Posts: 10
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I have a process that will be making connections to three different dabases using JNDI w/ Weblogic. The first two connections seemed fine and my code ran for months:

1) Connects to an Oracle db using XA driver (select only)
2) Connects to an Oracle db and then to another db using DBlink. This is a non-XA driver (again select only). I think I remember getting an error trying to use XA with a DBlink?

Now I'm trying to write a third connection to a mySQL database that will be performing inserts based on the data from the 2nd connection. I've tried to set up this connection as both a 1-phase and 2-phase commit without much luck. The error I'm getting says the context is already open for another transaction... however I'm closing all my connections after I'm through with them.

How am I to handle this? Thanks
 
Eugene Wright
Greenhorn
Posts: 10
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Resolved by switching mySQL driver to com.mysql.jdbc.jdbc2.optional.MysqlXADataSource
reply
    Bookmark Topic Watch Topic
  • New Topic