Return-Path: Delivered-To: apmail-logging-log4j-user-archive@www.apache.org Received: (qmail 38182 invoked from network); 25 May 2004 22:44:11 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 25 May 2004 22:44:11 -0000 Received: (qmail 46387 invoked by uid 500); 25 May 2004 22:44:42 -0000 Delivered-To: apmail-logging-log4j-user-archive@logging.apache.org Received: (qmail 46303 invoked by uid 500); 25 May 2004 22:44:41 -0000 Mailing-List: contact log4j-user-help@logging.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Log4J Users List" Reply-To: "Log4J Users List" Delivered-To: mailing list log4j-user@logging.apache.org Received: (qmail 46287 invoked by uid 98); 25 May 2004 22:44:41 -0000 Received: from Paul.Smith@lawlex.com.au by hermes.apache.org by uid 82 with qmail-scanner-1.20 (clamuko: 0.70. Clear:RC:0(202.92.123.11):. Processed in 0.123123 secs); 25 May 2004 22:44:41 -0000 X-Qmail-Scanner-Mail-From: Paul.Smith@lawlex.com.au via hermes.apache.org X-Qmail-Scanner: 1.20 (Clear:RC:0(202.92.123.11):. Processed in 0.123123 secs) Received: from unknown (HELO ike.local.anstat.com.au) (202.92.123.11) by hermes.apache.org with SMTP; 25 May 2004 22:44:41 -0000 Received: by ike.local.anstat.com.au with Internet Mail Service (5.5.2655.55) id ; Wed, 26 May 2004 08:43:57 +1000 Message-ID: <7395B46C07F8D51182AE000629570CC4B2E604@ike.local.anstat.com.au> From: Paul Smith To: 'Log4J Users List' Subject: RE: JMSReceiver - chainsaw Date: Wed, 26 May 2004 08:43:52 +1000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2655.55) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: hermes.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N > I'm now trying to evaluate the JMSReceiver - someone here > raised the issue that the SocketHubAppender/Receiver is not > password protected, and also there are concerns over the > possible performance impact if lots of people decide to > connect for remote monitoring over a (potentially) slow > network connection. I'm hoping that I can address these > points by switching to JMS. > > Problem is, org.apache.log4j.net.JMSReceiver doesn't get > distributed with the webstart chainsaw jars as far as I can > tell (and I'm having problems accessing apache cvs at the moment). > > Is there a particular reason why the JMSReceiver isn't part > of the distribution? Stephen, I have recently committed a change so that JMSReceiver is included as a 'known' Receiver, but I have NOT created and uploaded a new Web start version as yet. I am wondering whether you could do me a favour and test this change from CVS? You should be able to do this easily if you have not already got a local cvs copy: * downloand the ant install script available from the chainsaw page on the website and run it so you have the local copy. * Make sure you copy the build.properties.sample file -> build.properties and edit it so that the 'jms.jar' property points to your jar containing the jms stuff. (or chuck the jar in your system classpath, which you will need to do anyway for the web start version). * ant chainsaw Hopefully you will see that the JMSReceiver is then picked up as a known receiver and you can create it. If this proves successful, then I will go ahead and create and sign a web start version. Let me know how you go. cheers, Paul Smith --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org For additional commands, e-mail: log4j-user-help@logging.apache.org