[jboss-jira] [JBoss JIRA] Updated: (JBAS-3633) Tidyup logging when transaction is no longer active
Adrian Brock (JIRA)
jira-events at lists.jboss.org
Fri Jun 15 11:11:22 EDT 2007
[ http://jira.jboss.com/jira/browse/JBAS-3633?page=all ]
Adrian Brock updated JBAS-3633:
-------------------------------
Fix Version/s: JBossAS-4.2.1.CR1
> Tidyup logging when transaction is no longer active
> ---------------------------------------------------
>
> Key: JBAS-3633
> URL: http://jira.jboss.com/jira/browse/JBAS-3633
> Project: JBoss Application Server
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: JB5-Transaction Manager
> Affects Versions: JBossAS-4.0.5.CR1
> Reporter: Adrian Brock
> Priority: Minor
> Fix For: JBossAS-4.2.1.CR1
>
>
> Since JBossTM rollsback transactions at transaction timeout,
> we need to tidyup the transaction demarcation code (commit/rollback/setRollbackOnly, etc)
> such that the logging is more information and not so noisy.
> We still need to communicate that the transaction rolled back even if it is not
> the transaction demarcation point that does the rollback.
> Currrently, you get errors/warnings about not being able to setRollbackOnly or rollback,
> because the transaction is already ended.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list