[jboss-dev-forums] [Design of JCA on JBoss] - Re: JBossTS/JBossJCA XA/Local transactions

[bill.burke@jboss.com]

"mark.little at jboss.com" wrote : "weston.price at jboss.com" wrote : anonymous wrote : 
  |   |   | Since, until recently I believe, the most popular OSS databases didn't support XA and/or a JDBC XA Driver, my $5.00 bet is that there is a percentage of users who will run smack into this with JBoss 5. I also bet that the majority of Arjuna customers required XA aware resources and thus never used DBs like MySQL and Postgres. 
  |   |   | 
  |   | 
  |   | Yes. You hit the proverbial nail right on the head. The big boys (ie Oracle, DB2) I don't worry about so much. Our open source brethren is my main concern especially since we are touting these DB's as an integral component to our unified 'stack'. 
  |   | 
  | 
  | So what you'd be after is something that allowed multiple one-phase resources but whenever a transaction saw more than one of them it said something like "WARNING: YOU ARE SERIOUSLY F*CKING WITH YOUR APPLICATION CONSISTENCY. BACK OFF, TAKE A VACATION AND THEN IF YOU ARE REALLY SURE YOU WANT TO DO THIS THEN CONSIDER YOURSELF WARNED."

Our JCA implementation already does this:

            log.warn("Prepare called on a local tx. Use of local transactions on a jta transaction with more than one branch may result in inconsistent data in some cases of failure.");

I thought this message had been turned off, I guess it was just clarified  I think the old message was something very cryptic like:

"You are not getting the behavior you expect"

And this confused the shit outta people.





View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3989400#3989400

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3989400