Return-Path: Mailing-List: contact commons-user-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list commons-user@jakarta.apache.org Received: (qmail 32440 invoked from network); 2 Apr 2003 18:40:30 -0000 Received: from icarus.apache.org (208.185.179.13) by daedalus.apache.org with SMTP; 2 Apr 2003 18:40:30 -0000 Received: (qmail 44986 invoked by uid 1059); 2 Apr 2003 18:40:29 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 2 Apr 2003 18:40:29 -0000 Date: Wed, 2 Apr 2003 10:40:29 -0800 (PST) From: "Craig R. McClanahan" To: Jakarta Commons Users List Subject: Re: Digester - JVM pre-1.4 warning In-Reply-To: <20030402031746.17368.qmail@web14808.mail.yahoo.com> Message-ID: <20030402103601.C41920@icarus.apache.org> References: <20030402031746.17368.qmail@web14808.mail.yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: localhost 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Tue, 1 Apr 2003, Jai PP wrote: > Date: Tue, 1 Apr 2003 19:17:46 -0800 (PST) > From: Jai PP > Reply-To: Jakarta Commons Users List > To: commons-user@jakarta.apache.org > Subject: Digester - JVM pre-1.4 warning > > I am using the Digester inside oracle database JVM ( > oracle provides a way where you can load your java > classes . When you run these classes they use oracle > JVM) > > I get the following Warning in log4j. Do you what this > message means ? Is this error is ignorable or it is a > nasty one > > 2003-04-01 19:10:18,704 WARN [Root Thread] > > (MethodUtils.java:583) - Cannot use JVM pre-1.4 access > bug workaround die to restrictive security manager. > MethodUtils contains a workaround to a problem on pre-1.4 JVMs where accessibility of public methods differs between directly compiled code and reflection-based dynamic access. We try to call the Method.setAccessible() method to tell the JVM that this method is really accessible. If you are running under a SecurityManager (and it sounds like you are, since you got a SecurityException), the code that you are running must be granted sufficient privileges in order to execute this call -- specifically, you must have a ReflectPermission named "suppressAccessChecks" at runtime. For a Sun JDK/JRE, you would set this sort of stuff up in a $JAVA_HOME/jre/lib/security/java.policy file. You'll have to consult the Oracle documentation on how to do that in their JVM. > thanks! > - Jai Craig >