directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Emmanuel Lecharny <elecha...@gmail.com>
Subject Re: ADS 1.5.2 - log4j ERRORs when first starting replicas
Date Thu, 31 Jan 2008 17:25:19 GMT
Simon.Temple@saaconsultants.com wrote:
>
> When using mitosis replication for ADS there is a period of time 
> during start-up when one replica cannot connect to another - because 
> separate machines rarely start at the same rate.
>
>  
>
> During this time, ClientConnectionManager logs ERRORs as MINA gets 
> 'Connection refused' socket errors.
>
>  
>
> I'd like to propose that the replication service only logs WARN 
> messages for this condition.
>
Makes sense.
>
>  
>
> We currently deploy ADS with a monitoring system that detects log4j 
> ERRORs and raises operator alerts - therefore we get a flood of alerts 
> when we first start our systems when configured for replication  :-(
>
I see where it can become to be a problem ;)
>
>  
>
> wdyt?  Can/should I create a JIRA entry?
>
Yes, it would be better. I just checked the code, it's a single word to 
change (s/error/warn), but as we have bigbang, trunk, plus Alex's 
sandbox, having a JIRA is a big plus !

-- 
--
cordialement, regards,
Emmanuel L├ęcharny
www.iktek.com
directory.apache.org



Mime
View raw message