Logging of cluster rpc method exceptions at warn level is incorrect
-------------------------------------------------------------------
Key: JBAS-1571
URL: http://jira.jboss.com/jira/browse/JBAS-1571
Project: JBoss Application Server
Type: Bug
Components: Clustering
Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final, JBossAS-4.0.1 SP1
Reporter: Scott M Stark
Assigned to: Scott M Stark
Fix For: JBossAS-5.0 Beta, JBossAS-4.0.2RC1, JBossAS-3.2.8 Final
The HAPartitionImpl handler for cluster rpc method invocations logs Exceptions
and Errors thrown from the reflected method invocation at warn level. This
results in spurious warnings when the underlying invocation throws an exception
as part of its normal operation. An example of where this occurs is when an
ha-sigleton binds a jndi entry into its node, and a client does a lookup of the
binding through ha-jndi. In a 3 node cluster A, B, C with the ha-singleton on
A, a ha-jndi request going to B will produce the following
NameNotFoundException on C:
06:52:07,359 WARN [DefaultPartition] javax.naming.NameNotFoundException:
TheSingleton not bound
These exceptions should be logged at trace level.
--
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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
JBoss-Development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-development
