This is the bug report on RMI &
security. Essentially, the Eclipse startup sequence needs to access a class'
protection domain to find where it is installed, and this is prohibited
by the RMI security policy.
equinox-dev-admin@xxxxxxxxxxx wrote on 02/15/2004
> I believe there is a known issue with using the RMI security manager
> in 2.1 (at least it sounds familiar to me). You should search
> bug database and mail/news archives. Also, note that this mailing
> list is for equinox developers. Equinox is the new 3.0 runtime
> most of the people here don't really know that much about the 2.1
> runtime. You might try the platform newsgroup.
> "Eime, Raymond (CAA)" <Raymond.Eime@xxxxxxxxxxxxxxxx>
> Sent by: equinox-dev-admin@xxxxxxxxxxx > 02/15/2004 09:48 PM >
> To >
> "'equinox-dev@xxxxxxxxxxx'" <equinox-dev@xxxxxxxxxxx>
> cc >
> Subject >
> [equinox-dev] Tomcat plugin RMI security problem >
> I'm having a problem setting up my eclipse-tomcat debugging
> I'm using Eclipse 2.1.0 with sysdeo tomcat plugin 2.2.1 & running
> 4.1.24 all running in a Windows 2000 environment.
> I'm also using an RMI server to do work for my application while in
> development stage. I should also mention I'm not using java
> my application at this point.
> When I start a standalone tomcat server I have no problem using my
> but when I start tomcat within Eclipse and my code trys to create
> RMISecurity manager, ie execute "System.setSecurityManager(new
> RMISecurityManager());" I get an access denied exception thrown
> java.security.AccessControlContext class.
> eg java.security.AccessControlException: access denied
> (java.util.PropertyPermission catalina.base read)
> I have granted all permissions on my java.policy in both my tomcat
> & the RMI server. I've tried setting the system variable
> "java.security.policy" to point to my java.policy file from
> application code as a last resort and still no success.
> I hope someone can be of assistance.
> Ray Eime
> equinox-dev mailing list