Return-Path: X-Original-To: apmail-logging-log4net-dev-archive@www.apache.org Delivered-To: apmail-logging-log4net-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B327010163 for ; Thu, 17 Oct 2013 15:01:30 +0000 (UTC) Received: (qmail 5048 invoked by uid 500); 17 Oct 2013 15:01:30 -0000 Delivered-To: apmail-logging-log4net-dev-archive@logging.apache.org Received: (qmail 5019 invoked by uid 500); 17 Oct 2013 15:01:29 -0000 Mailing-List: contact log4net-dev-help@logging.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: "Log4NET Dev" List-Id: Delivered-To: mailing list log4net-dev@logging.apache.org Received: (qmail 5011 invoked by uid 99); 17 Oct 2013 15:01:28 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Oct 2013 15:01:28 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of phowe@paychex.com designates 141.123.220.33 as permitted sender) Received: from [141.123.220.33] (HELO mailin12.paychex.com) (141.123.220.33) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Oct 2013 15:01:22 +0000 DKIM-Signature: v=1; a=rsa-sha256; d=paychex.com; s=032013.paychex.com; c=relaxed/simple; q=dns/txt; i=@paychex.com; t=1382022060; x=1413558060; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=cO0qPcKgZ5TbwGiGLDp8tK2nsappDWZp9D8fQqNfNmA=; b=Z5wigWW1jUhs1GYlpBjViM2nXl/c+bqDhG4AEghtUM592hYRV6reAndRQfDVfixn n8NDhbgAEYqpZtMOGtMGCKNYLZvjfXHOLoyAuUvxdzd/RkZUz9eLgBW1qa9F+9ut oLLqoF3cwUCz0k+FU1G7QdNROcooJYIvb2MBGJU619c=; X-AuditID: ac10dc26-b7f408e0000009e4-51-525ffbace9b2 X-Server-Uuid: 49D65966-0291-4C37-B670-18BEA6276F97 From: "Howe, Peter L" To: "Log4NET Dev" Date: Thu, 17 Oct 2013 11:00:50 -0400 Subject: RE: Remote appender not sending Thread-Topic: Remote appender not sending Thread-Index: Ac7LR1bmZ8qfTe8zRteReIbbExuRpwAAbWSA Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 X-WSS-ID: 7E41242E2EO88944-01-01 Content-Type: multipart/alternative; boundary=_000_F1864A8DC815BB47AA000B23833CC91372AA59C963EXCHWEB1paych_ X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpjkeLIzCtJLcpLzFFi42LhYrrBprvmd3yQwezPiharvx1hc2D0aLq+ jz2AMYrLJiU1J7MstUjfLoEr48fDY8wFWxsZK26dbGBrYJxb3MXIySEhYCLR+XQlM4QtJnHh 3no2CNtY4vX9g4wgNpuApsSSYx9YQWwRASOJ4/1rWEBsFgFViRcHGsBqhAU0JD6suMzUxcgB VKMpsWCXCkz5lWeLGEHCvAK+EkcvFICEhYDMCTcegnVyCvhJvJr1EGwrI9AF30+tYQKxmQXE JW49mc8EcY2gxKLZe+Cu/LcLpl5U4k77erA5vEA1J2c+YYGoUZBY/ms6O8ScXIkvG/oYJzCK zEIydhaSlllIyiBsHYmGT4uZIGxtiWULXzPPAvoAxG5bpIAsvICRfRWjSG5iZk5mnqGRXkFi ZXJGaoVecn7uJkZg7KwRuKO2g3F6h+EhRgEORiUeXocPcUFCrIllxZW5hxglOJiVRHhd7scH CfGmJFZWpRblxxeV5qQWH2KU5mBREud9pTYxUEggPbEkNTs1tSC1CCbLxMEp1cDYwMnctEBM fYPr/Pde/59tiOWI/HN1bd+beB/2FvkDHD86OdjOTX2t/56z8pmw/JXXbNx+AT135/GEfj0f 3rmote+3VMLvvVNCv8cvFXx/yXoN8/0C5QTnpZ9Pf/u3avKOaRoLDHXs89MFLuyJbXCXk43K FbETPOLrtE/nZcjq9jPyZ46seyypxFKckWioxVxUnAgAxl1HfpkCAAA= X-Virus-Checked: Checked by ClamAV on apache.org --_000_F1864A8DC815BB47AA000B23833CC91372AA59C963EXCHWEB1paych_ Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable I also set up my test client to call LogManager.Shutdown( ) separately from= closing the application, with pauses in between things. After calling shu= tdown (and a long timeout), this message was displayed on the client: log4net: Hierarchy: Shutdown called on Hierarchy [log4net-default-repositor= y] log4net:ERROR [TimedRemotingAppender] RemotingAppender [RemotingAppender] f= ailed to send all queued events before close, in OnClose. However, all four of the previously mentioned connections remain establishe= d until the client application itself closes, at which point those connecti= ons disappear. Peter From: Howe, Peter L Sent: Thursday, October 17, 2013 10:44 AM To: Log4NET Dev Subject: Remote appender not sending Importance: High OK, here is my situation. I have a server process written that listens on the correct port for a remo= ting connection. I see it in NETSTAT: TCP 0.0.0.0:8085 DEV-D-21F7T:0 LISTENI= NG 884 My test application makes a few calls to log4net. I have implemented the T= imedRemotingAppender shown in these posts: http://apache-logging.6191.n7.nabble.com/Remote-Appender-td22810.html As expected, nothing happens in Remoting until the timer expires. I made f= our logging calls in the test client. I put a breakpoint in the TimedRemot= ingAppender.Append method to make sure it gets called - it is getting calle= d all four times. Each time it calls base.Append. Once the timer expires= and the flush( ) method is called, Remote connections show up in NETSTAT: TCP 127.0.0.1:8085 DEV-D-21F7T:52589 ESTABLISHED 884 TCP 127.0.0.1:8085 DEV-D-21F7T:52590 ESTABLISHED 884 TCP 127.0.0.1:8085 DEV-D-21F7T:52591 ESTABLISHED 884 TCP 127.0.0.1:8085 DEV-D-21F7T:52592 ESTABLISHED 884 TCP 127.0.0.1:52589 DEV-D-21F7T:8085 ESTABLISHED 7268 TCP 127.0.0.1:52590 DEV-D-21F7T:8085 ESTABLISHED 7268 TCP 127.0.0.1:52591 DEV-D-21F7T:8085 ESTABLISHED 7268 TCP 127.0.0.1:52592 DEV-D-21F7T:8085 ESTABLISHED 7268 I see a separate remoting connection here for each of the four log events, = however IRemoteLoggingSink.LogEvents( ) is never called on the server. Thi= ngs are getting lost somewhere in the bowels of log4net, even though it LOO= KS like Remoting connections are being made. Can anyone point me in the right direction as far as where to look? Thanks, Peter The information contained in this message may be privileged, confidential a= nd protected from disclosure. If the reader of this message is not the inte= nded recipient, or an employee or agent responsible for delivering this mes= sage to the intended recipient, you are hereby notified that any disseminat= ion, distribution or copying of this communication is strictly prohibited. = If you have received this communication in error, please notify your repres= entative immediately and delete this message from your computer. Thank you. --_000_F1864A8DC815BB47AA000B23833CC91372AA59C963EXCHWEB1paych_ Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: quoted-printable

I also se= t up my test client to call LogManager.Shutdown( ) separately from closing = the application, with pauses in between things.  After calling shutdow= n (and a long timeout), this message was displayed on the client:

 

log4net: Hierarchy: Shutdow= n called on Hierarchy [log4net-default-repository]

log4net:ERROR [TimedRem= otingAppender] RemotingAppender [RemotingAppender] failed=

to send all que= ued events before close, in OnClose.

 

However, all four of the previously mentioned connectio= ns remain established until the client application itself closes, at which = point those connections disappear.

 

Peter=

 

 

From: Howe, Peter L
Sent: Thursday, October 17, 2013= 10:44 AM
To: Log4NET Dev
Subject: Remote appender not = sending
Importance: High

 

OK, here is = my situation.

 <= /o:p>

I have a server process written= that listens on the correct port for a remoting connection.  I see it= in NETSTAT:

 

      &= nbsp;        TCP    0.0.0= .0:8085           DEV-D-2= 1F7T:0          LISTENING = ;      884

 

My test a= pplication makes a few calls to log4net.  I have implemented the Timed= RemotingAppender shown in these posts:

 

http://apache-logging.6191.n7.nabble.com/Remote-App= ender-td22810.html

 = ;

As expected, nothing happens = in Remoting until the timer expires.  I made four logging calls in the= test client.  I put a breakpoint in the TimedRemotingAppender.Append = method to make sure it gets called – it is getting called all four ti= mes.  Each time it calls base.Append.   Once the timer expir= es and the flush( ) method is called, Remote connections show up in NETSTAT= :

 =

  TCP =    127.0.0.1:8085        = DEV-D-21F7T:52589      ESTABLISHED  &nb= sp;  884

  TCP    127.0.0.1:8085   = ;      DEV-D-21F7T:52590    &n= bsp; ESTABLISHED     884

  TCP   = 127.0.0.1:8085         DEV-D-21F7T= :52591      ESTABLISHED     88= 4

  TCP    127.0.0.1:8085     = ;    DEV-D-21F7T:52592      ESTABLI= SHED     884

  TCP    127.0.0.1:52= 589        DEV-D-21F7T:8085  &= nbsp;    ESTABLISHED     7268=

  TC= P    127.0.0.1:52590      &nbs= p; DEV-D-21F7T:8085       ESTABLISHED &n= bsp;   7268

  TCP    127.0.0.1:52591 &n= bsp;      DEV-D-21F7T:8085    =    ESTABLISHED     7268

=

  TCP &nbs= p;  127.0.0.1:52592        DEV-D-21= F7T:8085       ESTABLISHED   &= nbsp; 7268

 

I see a= separate remoting connection here for each of the four log events, however= IRemoteLoggingSink.LogEvents( ) is never called on the server.  Thing= s are getting lost somewhere in the bowels of log4net, even though it LOOKS= like Remoting connections are being made.

 

Ca= n anyone point me in the right direction as far as where to look?

 

Thanks,

Peter

 =

The information contained in this message may be privileged, = confidential and protected from disclosure. If the reader of this message i= s not the intended recipient, or an employee or agent responsible for deliv= ering this message to the intended recipient, you are hereby notified that = any dissemination, distribution or copying of this communication is strictl= y prohibited. If you have received this communication in error, please noti= fy your representative immediately and delete this message from your comput= er. Thank you.

= --_000_F1864A8DC815BB47AA000B23833CC91372AA59C963EXCHWEB1paych_--