[jbosscache-issues] [JBoss JIRA] Reopened: (JBCACHE-1429) CacheStatus shouldn't WARN if recursive call made to isXXXAllowed()
Manik Surtani (JIRA)
jira-events at lists.jboss.org
Thu Oct 23 14:01:20 EDT 2008
[ https://jira.jboss.org/jira/browse/JBCACHE-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Manik Surtani reopened JBCACHE-1429:
------------------------------------
> CacheStatus shouldn't WARN if recursive call made to isXXXAllowed()
> -------------------------------------------------------------------
>
> Key: JBCACHE-1429
> URL: https://jira.jboss.org/jira/browse/JBCACHE-1429
> Project: JBoss Cache
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 2.2.1.CR2, 3.0.0.CR1
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Priority: Minor
> Fix For: 2.2.1.GA, 3.0.0.CR2, 3.0.0.GA
>
>
> For example, isStopAllowed() shouldn't warn if current state is STOPPING. It's easy for a CacheJmxWrapper to end up triggering a call to that method while the cache is stopping; happens all the time in the AS, resulting in spurious WARN logs. Such a call is a normal reentrance check and should be logged at DEBUG; WARN should be reserved for truly odd stuff like calling isStopAllowed() while CREATING, which likely indicates a coding problem.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosscache-issues
mailing list