RE: SocketHubAppender client
Actualy I agree, the 0.9.7 tarball is ancient (over 6 months at the least)... and that also happens to be the latest tag in CVS :( I haven't deared use the latest CVS snapshot for fear of breaking existing code; An uptodate/tested release would be very welcome by quite a few of us... Paul -Mensaje original- De: [mailto:[EMAIL PROTECTED] Enviado el: Friday, 19 November 2004 9:19 PM Para: log4cxx-user@logging.apache.org Asunto: RE: SocketHubAppender client Dear Paul: Great! Thanks for your patch, I have modified these lines, then recompiled it. Now it works well on my system. It seems that I must update code with cvs. The release bz2 tarball is too old. :) Regards, Sun Xiaoguang From: Paul Nader [EMAIL PROTECTED] Reply-To: Log4CXX User log4cxx-user@logging.apache.org To: 'Log4CXX User' log4cxx-user@logging.apache.org Subject: RE: SocketHubAppender client Date: Fri, 19 Nov 2004 20:52:48 +0100 Anton, Thinking back to it I actually reported a fault in sockethubappender. Here is my email to Michael... Maybe its still faulty? Paul. Hi Michal, I've been doing a bit more testing with log4cxx and noticed that sockethubappender didn't seem to work. I investigated and found that the oosList was not been passed by reference to the ServerMonitor. I made a diff of my changes in case you are interested: bash-2.03$ diff net/sockethubappender.h /export/home3/pnader/log4cxx-0.9.7/include/log4cxx/net/socketh ubappender.h 198c198 std::vectorhelpers::SocketOutputStreamPtr oosList; --- std::vectorhelpers::SocketOutputStreamPtr oosList; 210c210 const std::vectorhelpers::SocketOutputStreamPtr oosList); --- std::vectorhelpers::SocketOutputStreamPtr oosList); bash-2.03$ diff sockethubappender.cpp /export/home3/pnader/log4cxx-0.9.7/src/sockethubappender.cpp 165c165 SocketHubAppender::ServerMonitor::ServerMonitor(int port, const std::vectorhelpers::SocketOutputStreamPtr oosList) --- SocketHubAppender::ServerMonitor::ServerMonitor(int port, std::vectorhelpers::SocketOutputStreamPtr oosList) -Mensaje original- De: [mailto:[EMAIL PROTECTED] Enviado el: Friday, 19 November 2004 8:26 PM Para: log4cxx-user@logging.apache.org Asunto: RE: SocketHubAppender client I think may there are something wrong with my SocketHubAppender in my server side. I have tried your code. But it show nothing. Are there any error in my properties file? Thanks! here it is my properties file. log4j.rootLogger=debug, hls, hub log4j.hds.hdsconfig=debug, hls, hub log4j.hds.hdsconfig=debug, hls, hub log4j.appender.hls=org.apache.log4j.SocketAppender log4j.appender.hls.RemoteHost=localhost log4j.appender.hls.Port=4560 log4j.appender.hub=org.apache.log4j.SocketHubAppender log4j.appender.hub.Port=4561 From: [EMAIL PROTECTED] Reply-To: Log4CXX User log4cxx-user@logging.apache.org To: log4cxx-user@logging.apache.org CC: [EMAIL PROTECTED] Subject: SocketHubAppender client Date: Fri, 19 Nov 2004 14:04:17 -0500 Someone had asked a couple of days ago regarding the sockethubappender. I got this from our developer who was using the sockethubappender... BTW -- did you setup a socket hub appender configuration in your server side before tryingto connect? Renny Koshy President CEO RUBIX Information Technologies, Inc. www.rubixinfotech.com CdrSocketClient.cpp _ MSN Explorer: http://explorer.msn.com/lccn/ _ MSN Messenger: http://messenger.msn.com/cn
RE: SocketHubAppender client
I think the fact that the latest code may or may not compile is consistent with the email from the maintainers... Renny Koshy President CEO RUBIX Information Technologies, Inc. www.rubixinfotech.com [EMAIL PROTECTED] 11/19/2004 04:00 PM Please respond to Log4CXX User To:log4cxx-user@logging.apache.org cc: Subject:RE: SocketHubAppender client Paul, Yes, I have just checked out the last code. Yet, the automake complains that there are some error in configure.in. So do I fear about breaking existing work. Than I chose to modify the original 0.9.7 codes. BTW: Several days ago, I find 0.9.7 code cannot be compiled under freebsd. I add some platform case compile code to solve it. It seems we all need a new release. Sun From: Paul Nader [EMAIL PROTECTED] Reply-To: Log4CXX User log4cxx-user@logging.apache.org To: 'Log4CXX User' log4cxx-user@logging.apache.org Subject: RE: SocketHubAppender client Date: Fri, 19 Nov 2004 21:50:11 +0100 Actualy I agree, the 0.9.7 tarball is ancient (over 6 months at the least)... and that also happens to be the latest tag in CVS :( I haven't deared use the latest CVS snapshot for fear of breaking existing code; An uptodate/tested release would be very welcome by quite a few of us... Paul -Mensaje original- De: ? ? [mailto:[EMAIL PROTECTED] Enviado el: Friday, 19 November 2004 9:19 PM Para: log4cxx-user@logging.apache.org Asunto: RE: SocketHubAppender client Dear Paul: Great! Thanks for your patch, I have modified these lines, then recompiled it. Now it works well on my system. It seems that I must update code with cvs. The release bz2 tarball is too old. :) Regards, Sun Xiaoguang From: Paul Nader [EMAIL PROTECTED] Reply-To: Log4CXX User log4cxx-user@logging.apache.org To: 'Log4CXX User' log4cxx-user@logging.apache.org Subject: RE: SocketHubAppender client Date: Fri, 19 Nov 2004 20:52:48 +0100 Anton, Thinking back to it I actually reported a fault in sockethubappender. Here is my email to Michael... Maybe its still faulty? Paul. Hi Micha?, I've been doing a bit more testing with log4cxx and noticed that sockethubappender didn't seem to work. I investigated and found that the oosList was not been passed by reference to the ServerMonitor. I made a diff of my changes in case you are interested: bash-2.03$ diff net/sockethubappender.h /export/home3/pnader/log4cxx-0.9.7/include/log4cxx/net/socketh ubappender.h 198c198 std::vectorhelpers::SocketOutputStreamPtr oosList; --- std::vectorhelpers::SocketOutputStreamPtr oosList; 210c210 const std::vectorhelpers::SocketOutputStreamPtr oosList); --- std::vectorhelpers::SocketOutputStreamPtr oosList); bash-2.03$ diff sockethubappender.cpp /export/home3/pnader/log4cxx-0.9.7/src/sockethubappender.cpp 165c165 SocketHubAppender::ServerMonitor::ServerMonitor(int port, const std::vectorhelpers::SocketOutputStreamPtr oosList) --- SocketHubAppender::ServerMonitor::ServerMonitor(int port, std::vectorhelpers::SocketOutputStreamPtr oosList) -Mensaje original- De: ?? ??? [mailto:[EMAIL PROTECTED] Enviado el: Friday, 19 November 2004 8:26 PM Para: log4cxx-user@logging.apache.org Asunto: RE: SocketHubAppender client I think may there are something wrong with my SocketHubAppender in my server side. I have tried your code. But it show nothing. Are there any error in my properties file? Thanks! here it is my properties file. log4j.rootLogger=debug, hls, hub log4j.hds.hdsconfig=debug, hls, hub log4j.hds.hdsconfig=debug, hls, hub log4j.appender.hls=org.apache.log4j.SocketAppender log4j.appender.hls.RemoteHost=localhost log4j.appender.hls.Port=4560 log4j.appender.hub=org.apache.log4j.SocketHubAppender log4j.appender.hub.Port=4561 From: [EMAIL PROTECTED] Reply-To: Log4CXX User log4cxx-user@logging.apache.org To: log4cxx-user@logging.apache.org CC: [EMAIL PROTECTED] Subject: SocketHubAppender client Date: Fri, 19 Nov 2004 14:04:17 -0500 Someone had asked a couple of days ago regarding the sockethubappender. I got this from our developer who was using the sockethubappender... BTW -- did you setup a socket hub appender configuration in your server side before tryingto connect? Renny Koshy President CEO RUBIX Information Technologies, Inc. www.rubixinfotech.com CdrSocketClient.cpp
RE: SocketHubAppender client
Title: Mensaje Yes, I also checked the log4cxx Dev mailing listand it would seem new release is in the works... -Mensaje original-De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Enviado el: Friday, 19 November 2004 10:02 PMPara: Log4CXX UserAsunto: RE: SocketHubAppender clientI think the fact that the latest code may or may not compile is consistent with the email from the maintainers... Renny KoshyPresident CEORUBIX Information Technologies, Inc.www.rubixinfotech.com [EMAIL PROTECTED] 11/19/2004 04:00 PM Please respond to "Log4CXX User" To: log4cxx-user@logging.apache.org cc: Subject:RE: SocketHubAppender clientPaul,Yes, I have just checked out the last code. Yet, the automake complains that there are some error in configure.in. So do I fear about breaking existing work. Than I chose to modify the original 0.9.7 codes.BTW: Several days ago, I find 0.9.7 code cannot be compiled under freebsd. I add some platform case compile code to solve it. It seems we all need a new release.SunFrom: "Paul Nader" [EMAIL PROTECTED]Reply-To: "Log4CXX User" log4cxx-user@logging.apache.orgTo: "'Log4CXX User'" log4cxx-user@logging.apache.orgSubject: RE: SocketHubAppender clientDate: Fri, 19 Nov 2004 21:50:11 +0100Actualy I agree, the 0.9.7 tarball is ancient (over 6 months at the least)... and that also happens to be the latest tag in CVS :( I haven't deared use the latest CVS snapshot for fear of breaking existing code; An uptodate/tested release would be very welcome by quite a few of us...Paul -Mensaje original- De: [mailto:[EMAIL PROTECTED] Enviado el: Friday, 19 November 2004 9:19 PM Para: log4cxx-user@logging.apache.org Asunto: RE: SocketHubAppender clientDear Paul: Great! Thanks for your patch, I have modified these lines, then recompiled it. Now it works well on my system. It seems that I must update code with cvs. The release bz2 tarball is too old. :) Regards, Sun Xiaoguang From: "Paul Nader" [EMAIL PROTECTED] Reply-To: "Log4CXX User" log4cxx-user@logging.apache.org To: "'Log4CXX User'" log4cxx-user@logging.apache.org Subject: RE: SocketHubAppender client Date: Fri, 19 Nov 2004 20:52:48 +0100Anton, Thinking back to it I actually reported a fault in sockethubappender. Here is my email to Michael... Maybe its still faulty? Paul.Hi Micha, I've been doing a bit more testing with log4cxx and noticed that sockethubappender didn't seem to work. I investigated and found that the oosList was not been passed by reference to the ServerMonitor. I made a diff of my changes in case you are interested: bash-2.03$ diff net/sockethubappender.h /export/home3/pnader/log4cxx-0.9.7/include/log4cxx/net/socketh ubappender.h 198c198 std::vectorhelpers::SocketOutputStreamPtr oosList; --- std::vectorhelpers::SocketOutputStreamPtr oosList; 210c210 const std::vectorhelpers::SocketOutputStreamPtr oosList); --- std::vectorhelpers::SocketOutputStreamPtr oosList); bash-2.03$ diff sockethubappender.cpp /export/home3/pnader/log4cxx-0.9.7/src/sockethubappender.cpp 165c165 SocketHubAppender::ServerMonitor::ServerMonitor(int port, const std::vectorhelpers::SocketOutputStreamPtr oosList) --- SocketHubAppender::ServerMonitor::ServerMonitor(int port, std::vectorhelpers::SocketOutputStreamPtr oosList) -Mensaje original- De: [mailto:[EMAIL PROTECTED] Enviado el: Friday, 19 November 2004 8:26 PMPara: log4cxx-user@logging.apache.orgAsunto: RE: SocketHubAppender client I think may there are something wrong with my SocketHubAppender inmy server side. I have tried your code. But it show nothing. Arethere any error in my properties file? Thanks! here it is my properties file. log4j.rootLogger=debug, hls, hub log4j.hds.hdsconfig=debug, hls, hub log4j.hds.hdsconfig=debug, hls,hub log4j.appender.hls=org.apache.log4j.SocketAppender log4j.appender.hls.RemoteHost=localhost log4j.appender.hls.Port=4560 log4j.appender.hub=org.apache.log4j.SocketHubAppender log4j.appender.hub.Port=4561 From: [EMAIL PROTECTED] Reply-To: "Log4CXX User" log4cxx-user@logging.apache.orgTo: log4cxx-user@logging.apache.orgCC: [EMAIL PROTECTED]Subject: SocketHubAppender clientDate: Fri, 19 Nov 2004 14:04:17 -0500Someone had asked a couple of days ago regarding the sockethubappender.I got this from our devel
