[
http://jira.jboss.com/jira/browse/JBCACHE-1185?page=all ]
Brian Stansberry closed JBCACHE-1185.
-------------------------------------
Fix Version/s: (was: 2.1.0.GA)
Resolution: Rejected
The logging level was correct; the WARN messages that were seen were due to a different
condition than I'd thought where the WARN was valid.
Reduce logging level when a lifecycle operation is performed twice
------------------------------------------------------------------
Key: JBCACHE-1185
URL:
http://jira.jboss.com/jira/browse/JBCACHE-1185
Project: JBoss Cache
Issue Type: Task
Security Level: Public(Everyone can see)
Affects Versions: 2.0.0.GA
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Priority: Minor
We log a WARN when, for example, stop() is invoked when the cache is already stopped.
But this can happen easily (and validly) when the JMX wrappers are used with the
microcontainer. MC stops the Cache and then the wrapper is stopped, which calls through
to the Cache. This kind of thing is normal and we handle it properly, so we shouldn't
log a warn.
Perhaps having the wrappers test the cache status before invoking on it would be better;
that way we can still warn in other situations.
--
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