[jboss-jira] [JBoss JIRA] (AS7-3172) Logging incosistency "WARN" vs "WARNING"
Radoslav Husar (JIRA)
jira-events at lists.jboss.org
Wed Feb 8 11:31:49 EST 2012
[ https://issues.jboss.org/browse/AS7-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Radoslav Husar closed AS7-3172.
-------------------------------
> Logging incosistency "WARN" vs "WARNING"
> ----------------------------------------
>
> Key: AS7-3172
> URL: https://issues.jboss.org/browse/AS7-3172
> Project: Application Server 7
> Issue Type: Bug
> Components: Logging
> Affects Versions: 7.1.0.CR1
> Reporter: Radoslav Husar
> Assignee: David Lloyd
> Priority: Minor
> Labels: usability
>
> AS7 internally logs as warn like this
> {noformat}
> 12:24:10,959 WARNING [org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher] (MSC service thread 1-11) Channel Muxer already has a default up handler installed (org.jboss.as.clustering.jgroups.ClassLoaderAwareUpHandler at f5ad7f4) but now it is being overridden
> {noformat}
> but projects like Infinispan end up logging
> {noformat}
> 12:28:22,463 WARN [org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher] Problems unmarshalling remote command from byte buffer: org.infinispan.CacheException: Cache manager is either starting up or shutting down but it's not interrupted, so type (id=74) cannot be resolved.
> {noformat}
> and this is inconsistent and is a usability issue for people analying logs (like myself).
> How is this handled, what can be done here?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list