> 2009-10-06 10:36:32,582 ERROR [org.hibernate.transaction.JTATransaction] -
> JTA commit failed
> java.lang.IllegalStateException:
> [com.arjuna.ats.internal.jta.transaction.arjunacore.inactive]
> [com.arjuna.ats.internal.jta.transaction.arjunacore.inactive] The
> transaction is not active!
If I recall correctly, this can occur when the JDBC driver throws an
exception for a database error, e.g. constraint violation, and
subsequently rolls back the database transaction. Sometimes the
rollback isn't transmitted to the wrapping transaction manager, arjuna
in this case, and when the transaction manager tries to commit or roll
back its consituents, it fails because the underlying DB transaction
has been rolled back, and is therefore not active. You could help
confirm this by searching the logs for JDBC errors that are previous
to the one you shared; your database logs might also contain helpful
hints to support or refute this theory.
M
--
You are currently subscribed to
[hidden email] as:
[hidden email]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-dev