Menu

#319 Fix for Bug 575966 (Failed commits)

v3.0 Rabbit Hole
closed-fixed
JBossTX (2)
5
2003-02-12
2002-11-27
Marcel
No

The problem is that failing commits are not reported.
This is because the XAException is swallowed on
XA_UNKNOWN error.

This patch checks if an unknown error occured upon
commit, and does not change the status from
STATUS_COMMITTING to a successful STATUS_COMMITTED.

Please note that the subsequent
javax.transaction.RollbackException is caught in
TxInterceptorCMT.java and rethrown as an
javax.ejb.TransactionRolledbackLocalException - I'm not
sure this is the right place but it works.

Discussion

  • Marcel

    Marcel - 2002-11-27

    Patch agains jboss-3.0.4

     
  • Marcel

    Marcel - 2003-02-12

    Patch against jboss 3.0.5

     
  • Marcel

    Marcel - 2003-02-12

    Logged In: YES
    user_id=657615

    Updated patch for 3.0.5 commit problem including an improved
    logging
    (you can see the original sql exception error message
    in the log file now, helpful if you want so see the cause
    of the commit failure).

     
  • David Jencks

    David Jencks - 2003-02-12
    • assigned_to: nobody --> d_jencks
    • status: open --> closed-fixed
     
  • David Jencks

    David Jencks - 2003-02-12

    Logged In: YES
    user_id=60525

    Sorry I didn't see this patch earlier.

    Can you check if the code in cvs for 3.0 covers all the functionality in your patch? Looking at the patch I think we have.

    The cvs code also uses jboss exception subclasses to link the exception the app gets back to the original sql or xa exception, and provides a customizable way of logging driver specific xa exceptions.

    I'm marking this closed, if I missed anything please speak up.

     

Log in to post a comment.

MongoDB Logo MongoDB