For what its worth, I am asking the JTA experts at JBossTS about the kosher-ness of calling setRollbackOnly from within the Synchronization prior to re-throwing the exception. That might just me being overly protective. And it seems to be the specific thing that causes WebLogic trouble.