[jboss-jira] [JBoss JIRA] Closed: (JBCACHE-982) WARN logged if app calls into cache during tx's afterCompletion() phase.
Brian Stansberry (JIRA)
jira-events at lists.jboss.org
Wed Feb 21 12:24:35 EST 2007
[ http://jira.jboss.com/jira/browse/JBCACHE-982?page=all ]
Brian Stansberry closed JBCACHE-982.
------------------------------------
Fix Version/s: 1.4.1.SP3
Resolution: Done
> WARN logged if app calls into cache during tx's afterCompletion() phase.
> ------------------------------------------------------------------------
>
> Key: JBCACHE-982
> URL: http://jira.jboss.com/jira/browse/JBCACHE-982
> Project: JBoss Cache
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 1.3.0.GA, 1.2.4, 1.4.0.GA, 1.2.4SP1, 1.2.4SP2, 1.3.0.SP1, 1.3.0.SP2, 1.3.0.SP3, 1.4.0.SP1, 1.4.1.GA, 1.3.0.SP4, 2.0.0.BETA1, 1.4.1.SP1, 1.4.1.SP2
> Reporter: Brian Stansberry
> Assigned To: Brian Stansberry
> Priority: Minor
> Fix For: 2.0.0.BETA2, 1.4.1.SP3
>
>
> CacheImpl.getCurrentTransaction() logs a WARN if the tx bound to the thread is Status.COMMITTED. It's a valid use case (see forum ref for an example) to want to call into the cache during a Synchronization's afterCompletion() callback, but doing so would trigger this WARN. So, if the tx is Status.COMMITTED, the log message should be a TRACE.
--
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