[jira] Resolved: (RIVER-334) jre 6 Policy issues

["Peter Firmstone (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/RIVER-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Peter Firmstone resolved RIVER-334.
-----------------------------------

    Workaround: Not Applicable  (was: Grant AllPermission to river/trunk/lib-ext directory in jinitest.policy and change static initialization blocks for class variables in PreferredClassProvider to lazy load at Object instantiation time.)
    Resolution: Fixed

The issue was due to earlier loading of the java SecurityManager and jsk-policy.jar, not being visible to the initial Policy implementation loaded by the JAVA 6 JRE.

Problem solved by specifically granting all permission in policy files to jsk-policy.jar

> jre 6 Policy issues
> -------------------
>
>                 Key: RIVER-334
>                 URL: https://issues.apache.org/jira/browse/RIVER-334
>             Project: River
>          Issue Type: Bug
>          Components: other
>    Affects Versions: AR3
>         Environment: In a Java 6 jre environment, when compiled with jdk1.6, and the compiler options -source=5 and target=jsr14.  Applicable to the Jini Test Harness (qa test harness)
>            Reporter: Peter Firmstone
>            Assignee: Peter Firmstone
>             Fix For: AR3
>
>   Original Estimate: 40h
>  Remaining Estimate: 40h
>
> The Java 6 environment loads it's own Policy implementation prior to the loading of any of the ApacheRiver Policy Provider implementations, so implies() permission checks are performed against the River policy implementations, which lack the required permission, causing failure.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.