Steen Lehmann wrote:
> Thanks Ashish, disabling the security manager does indeed fix the issue.
>
> On our test OC4J system the security manager's policy file grants an
> AllPermission to everybody:
> grant {
> permission java.security.AllPermission;
> };
>
> and I would expect that this is pretty much the same as using no
> security manager - but either that's not the case or the policy file
> is not being picked up correctly, or is overridden soTmewhere.
>
The policy file is not being picked up. The effect of grant-all
AllPermission is the same as
no security manager but there is the performance hit you're taking at
runtime to actually
go through the security checks but don't stop nobody ;)
> I guess I need to research what the default settings for security are
> on OC4J and add specific grants to that. Sigh, I thought Rails
> development was all about having fun ;-)
>
Well I know it's a pain but it should not take you more than a few
iterations to figure out the permission needed.
However, an authoritative list can only be provided by the JRuby folks
since you might be
missing some event paths in your tests that could potentially trigger
the need for
additional security privileges.
I would suggest that some of the JRuby tests be run with the security
manager enabled
to figure out the complete list of security permissions which should be
a relatively small set by my guess.
-Ashish
_______________________________________________
Jruby-extras-devel mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/jruby-extras-devel
