Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 39177 invoked from network); 31 Jan 2008 17:13:47 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 31 Jan 2008 17:13:47 -0000 Received: (qmail 55739 invoked by uid 500); 31 Jan 2008 17:13:38 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 55680 invoked by uid 500); 31 Jan 2008 17:13:38 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 55669 invoked by uid 99); 31 Jan 2008 17:13:38 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 31 Jan 2008 09:13:38 -0800 X-ASF-Spam-Status: No, hits=3.2 required=10.0 tests=FS_REPLICA,HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [194.75.234.2] (HELO smtpgate.saa-cons.co.uk) (194.75.234.2) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 31 Jan 2008 17:13:10 +0000 To: dev@directory.apache.org Subject: ADS 1.5.2 - log4j ERRORs when first starting replicas MIME-Version: 1.0 Date: Thu, 31 Jan 2008 17:13:21 +0000 Message-ID: From: Simon.Temple@saaconsultants.com Content-Type: multipart/alternative; boundary=alternative_NB3400_14022 X-WatchGuard-IPS: message checked X-Virus-Checked: Checked by ClamAV on apache.org --alternative_NB3400_14022 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline When using mitosis replication for ADS there is a period of time during s= tart-up when one replica cannot connect to another - because separate mac= hines rarely start at the same rate. = During this time, ClientConnectionManager logs ERRORs as MINA gets 'Conne= ction refused' socket errors. = I'd like to propose that the replication service only logs WARN messages = for this condition. = We currently deploy ADS with a monitoring system that detects log4j ERROR= s and raises operator alerts - therefore we get a flood of alerts when we= first start our systems when configured for replication :-( = = wdyt? Can/should I create a JIRA entry? = Regards = Simon Temple 2008-01-30 14:58:03,091 ERROR [org.apache.directory.mitosis.service.Clien= tConnectionManager](ClientConnectionManager-repl-sg@10.1.10.50:20846) [Re= plica-repl-ot] Failed to connect to replica-repl-sg org.apache.mina.common.RuntimeIOException: Failed to get the session. at org.apache.mina.common.support.DefaultConnectFuture.getSession(Defaul= tConnectFuture.java:56) at org.apache.directory.mitosis.service.ClientConnectionManager$Connecto= r.run(ClientConnectionManager.java:375) Caused by: java.net.ConnectException: Connection refused: no further info= rmation at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:527= ) at org.apache.mina.transport.socket.nio.SocketConnector.processSessions(= SocketConnector.java:275) at org.apache.mina.transport.socket.nio.SocketConnector.access$800(Socke= tConnector.java:53) at org.apache.mina.transport.socket.nio.SocketConnector$Worker.run(Socke= tConnector.java:362) at org.apache.mina.util.NamePreservingRunnable.run(NamePreservingRunnabl= e.java:51) at java.lang.Thread.run(Thread.java:595)= --alternative_NB3400_14022 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline

When using m= itosis = replication for ADS there is a period of time during start-up when one re= plica = cannot connect to another - because separate machines rarely start at the= same = rate.

During this time, = ClientConnectionManager logs ERRORs as MINA gets 'Connection refused' soc= ket = errors.

I'd like to propose that t= he = replication service only logs WARN messages for this = condition.

We currently deploy ADS wi= th a = monitoring system that detects log4j ERRORs and raises operator alerts = - therefore we get a flood of alerts when we first start our sy= stems = when configured for replication :-(

wdyt? Can/should I c= reate a = JIRA entry?

Regards<= /P>

Simon Temple

2008-01-30 14:58:03,091 ER= ROR = [org.apache.directory.mitosis.service.ClientConnectionManager](ClientCo= nnectionManager-repl-sg@10.1.10.50:20846) = [Replica-repl-ot] Failed to connect to = replica-repl-sg
org.apache.mina.common.RuntimeIOException: Failed to g= et the = session.
at = org.apache.mina.common.support.DefaultConnectFuture.getSession(DefaultCon= nectFuture.java:56)
at = org.apache.directory.mitosis.service.ClientConnectionManager$Connector.ru= n(ClientConnectionManager.java:375)
Caused = by: java.net.ConnectException: Connection refused: no further = information
at sun.nio.ch.SocketChannelImpl.checkConnect(Native = Method)
at = sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:527) at = org.apache.mina.transport.socket.nio.SocketConnector.processSessions(Sock= etConnector.java:275)
at = org.apache.mina.transport.socket.nio.SocketConnector.access$800(SocketCon= nector.java:53)
at = org.apache.mina.transport.socket.nio.SocketConnector$Worker.run(SocketCon= nector.java:362)
at = org.apache.mina.util.NamePreservingRunnable.run(NamePreservingRunnable.ja= va:51)
at = java.lang.Thread.run(Thread.java:595)

--alternative_NB3400_14022--