Thanks for your reply...but could this be the problem that is related to the Jasper ClassLoader Exception error I am getting when first accessing this page. After I refresh the page (this is after the Singleton instance of my object is created), the page loads up without any problems...
Could this be related to a Security Manager (or lack of) within the context of this application? Thanks Paul -----Original Message----- From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 30, 2002 7:17 PM To: Tomcat Users List Subject: RE: JasperLoader Exception On Wed, 30 Jan 2002, Pavel Brun wrote: > Date: Wed, 30 Jan 2002 18:34:41 -0500 > From: Pavel Brun <[EMAIL PROTECTED]> > Reply-To: Tomcat Users List <[EMAIL PROTECTED]> > To: Tomcat Users List <[EMAIL PROTECTED]> > Subject: RE: JasperLoader Exception > > thanks.....was it within code related to Tomcat? Or your own code that does > the calling to an RMI server??? > Tomcat 4 has zero calls to System.setSecurityManager in it. If you start it with the appropriate command line option (-security), the standard startup scripts add the following system property settings to the command line: -Djava.security.manager -Djava.security.policy==$CATALINA_BASE/conf/catalina.policy which tells the JVM to install a security manager at startup time, using the specified policy file as a replacement for the one in the JDK directory (that's what the '==' does). If you start Tomcat without a security manager, and some code that is executed calls System.setSecurityManager, that is exactly what the JVM does. (Of course, if somebody calls System.exit() it will shut down Tomcat as well :-). Moral of the story - you are advised to bone up on how security managers work in Java, and run Tomcat with the "-security" option at startup time. You'll need to add any permissions your apps require to the catalina.policy file (the default sandbox is fairly restrictive), but you can avoid some nasty things that bad code (or inadvertently called code) might do to you. Craig McClanahan > -----Original Message----- > From: Richard Bushell [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, January 30, 2002 6:12 PM > To: Tomcat Users List > Subject: RE: JasperLoader Exception > > > We had a similiar problem calling an RMI server from within Tomcat. It > turned out that deep down inside some library code there was a call to > System.setSecurityManager(...). > > Hope this helps. > > Richard > > > -----Original Message----- > From: Pavel Brun [mailto:[EMAIL PROTECTED]] > Sent: Thursday, January 31, 2002 9:36 AM > To: Tomcat Users List > Subject: RE: JasperLoader Exception > > > Hello all, > > Well...I did have a chance to get up a Website to try to prove my > example, > but I couldn't with the example I tried to show. > > It actually is a problem related to creating an object that queries an > LDAP server for certain attributes in order to use them later in the > application. > Does anybody know of any latency issues with regards to LDAP queries and > trying > to access an object that does this?? > > Thanks > > Paul > > -----Original Message----- > From: Pavel Brun [mailto:[EMAIL PROTECTED]] > Sent: Sunday, January 27, 2002 9:48 PM > To: Tomcat Users List > Subject: RE: JasperLoader Exception > > > Thanks...I will try to get one up as soon as possible. I will let you > know > when I have something up and running. > > Thanks > > Paul > > -----Original Message----- > From: Remy Maucherat [mailto:[EMAIL PROTECTED]] > Sent: Sunday, January 27, 2002 6:29 PM > To: Tomcat Users List > Subject: Re: JasperLoader Exception > > > > Hello all, > > > > I am new this this mailing list. I am developing software and am using > > Java Beans and Tags for this particular application. From time to > time, > > when I first access a particular page, I get a Class Loader exception > > when loading a class: > > > > java.lang.NullPointerException > > at > org.apache.jasper.servlet.JasperLoader.loadClass(JasperLoader.java:198) > > at > org.apache.jasper.servlet.JasperLoader.loadClass(JasperLoader.java:132) > > at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:313) > > at org.apache.jsp.settings$jsp._jspService(settings$jsp.java:115) > > . > > . I leave out these details because it does not bring any > > . value. > > . > > > > In this particular case, it crashed when trying to use the > "pageContext" > > variable name when using: pageContext.getAttribute() method. Does > anybody > > know what the root cause of a Jasper Loader exception is? Is it at all > > related to insantiating beans or using the <jsp:useBean> parameter? > > > > I have tried looking everywhere, but couldn't find any description or > > solutions.. > > Could you post a simple JSP file that would cause the problem ? > > Remy > > > -- > To unsubscribe: <mailto:[EMAIL PROTECTED]> > For additional commands: <mailto:[EMAIL PROTECTED]> > Troubles with the list: <mailto:[EMAIL PROTECTED]> > > > > -- > To unsubscribe: <mailto:[EMAIL PROTECTED]> > For additional commands: <mailto:[EMAIL PROTECTED]> > Troubles with the list: <mailto:[EMAIL PROTECTED]> > > > > > -- > To unsubscribe: <mailto:[EMAIL PROTECTED]> > For additional commands: <mailto:[EMAIL PROTECTED]> > Troubles with the list: <mailto:[EMAIL PROTECTED]> > > > -- > To unsubscribe: <mailto:[EMAIL PROTECTED]> > For additional commands: <mailto:[EMAIL PROTECTED]> > Troubles with the list: <mailto:[EMAIL PROTECTED]> > > > > -- > To unsubscribe: <mailto:[EMAIL PROTECTED]> > For additional commands: <mailto:[EMAIL PROTECTED]> > Troubles with the list: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]> -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
