I'm runnning Tomcat 3.2.1 on NT as a service. (JDK1.2.2_006)
My servlets make calls to EJB methods and as such require the
RMISecurityManager.
I start Tomcat using (among others) the following lines in
wrapper.properties:
wrapper.policy=$(wrapper.tomcat_home)\conf\tomcat.policy
wrapper.cmd_line=$(wrapper.javabin)
-Djava.security.manager=java.rmi.RMISecurityManager
-Djava.security.policy=$(wrapper.policy)
-Dtomcat.home=$(wrapper.tomcat_home) -classpath $(wrapper.class_path)
$(wrapper.startup_class) -config $(wrapper.server_xml) -home
$(wrapper.tomcat_home)
I know that this is starting Tomcat using the policy file because I get
different results when I add/remove permissions in this file.
So that I can just get the Servlets to work (and worry about clamping down
on security later) I've got the following line in tomcat.policy:
grant {
permission java.security.AllPermission;
};
This (i believe) grants all my webapps all permissions, so everything should
always work in this case?
However I get the following debug on my first EJB method call:
java.security.manager=java.rmi.RMISecurityManager
SM=java.rmi.RMISecurityManager@1f7522a1
javax.naming.NamingException: Failed to unmarshal proxy [Root exception is
java.lang.ClassNotFoundException: com.mypackage.MyClass_Stub]
I had exactly the same problem running under JavaWebServer2.0 but when the
AllPermission was added to the jserv.policy file it worked.
I've tried every combination I can think of to get this working, any help
would be appreciated.
Thanks, Rich.
**********************************************************************
Information in this email is confidential and may be privileged.
It is intended for the addressee only. If you have received it in error,
please notify the sender immediately and delete it from your system.
You should not otherwise copy it, retransmit it or use or disclose its
contents to anyone.
Thank you for your co-operation.
**********************************************************************
