Application Server Solutions for Microsoft IIS and ASP.NET
       solutions   products   partners   company   support   downloads         store
ServletExec Self-Help: FAQ
Back to Search >  Back to Search Results

Faq ID 41
Product ServletExec
Category Known Limitations and Workarounds, Security
Question Why am I seeing SecurityExceptions when using ServletExec with JDK 1.2 or higher ?
Answer JDK 1.2 has a different security scheme from JDK 1.1 so not all of the security settings for the Java VM are available on the ServletExec Security admin page. If you are seeing SecurityExceptions then you should edit the java.policy file to give permission to your servlet to perform the task it is trying to perform. If you want to give permission to your servlets to do everything then add the following to your java.policy file:

grant {

If you are using SE 3.x or 4.x then you may need to use the information given in SE FAQ #111

If you are using SE 2.2 with JRE or JDK 1.2.2, and you are seeing the following stacktrace in your browser when trying to access the SE admin pages: access denied (java.lang.RuntimePermission setContextClassLoader)
 at java.lang.SecurityManager.checkPermission(
 at java.lang.Thread.setContextClassLoader(
 at newatlanta.servletexec.ServletExec.processServletRequest(
 at newatlanta.servletexec.ServletExec.ProcessRequest(
 at newatlanta.servletexec.ServletExec.ProcessRequest(

then you should add the following to your java.policy file:

grant {
permission java.lang.RuntimePermission "setContextClassLoader";

See SE FAQ #112 for tips about where you can find your java.policy file. NOTE: This information is also discussed in the online bug report for SE bug #87 entitled: "Exception is thrown for every request when security manager is set to ServletExec's security manager"

company media information terms of use privacy policy contact us