Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 64277 invoked from network); 5 Jul 2002 23:06:02 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 5 Jul 2002 23:06:02 -0000 Received: (qmail 5876 invoked by uid 97); 5 Jul 2002 23:06:16 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 5846 invoked by uid 97); 5 Jul 2002 23:06:15 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 5831 invoked by uid 98); 5 Jul 2002 23:06:14 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Message-ID: <015101c22478$87d03580$6401a8c0@darden.virginia.edu> From: "Erik Hatcher" To: "Jakarta Commons Developers List" References: <20020703190342.D82844-100000@icarus.apache.org> Subject: Re: [betwixt / logging] SecurityException being thrown Date: Fri, 5 Jul 2002 19:05:59 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N ----- Original Message ----- From: "Craig R. McClanahan" > > I'd love to use more Commons stuff, but kinda tough when the SecurityManager > > won't let Commons Logging work. > > > > The most common cause for this was failure to catch and ignore an > exception while trying to read system properties in the 1.0 release > version of commons-logging. This has been fixed in the lastest nightly > builds (and I thought Costin was going to do a 1.0.1 to pick it up -- > guess that hasn't happened yet). Could you try a more recent > commons-logging.jar and see if it solves this problem for you? I wish I could say that it solves the problem, but it doesn't. I've upgraded to the latest nightly build and the result is the same. There are a few variables in my equation: I'm running a Java program which has a tight SecurityManager installed, and I've granted a policy file to the process. I see SecurityException being caught explicitly in LogFactory.getFactory() twice - does it need to be addd to the middle section also? Erik -- To unsubscribe, e-mail: For additional commands, e-mail: