harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gregory Shimansky (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HARMONY-765) [drlvm] incorrect initialization of default domain in j.l.ClassLoader
Date Wed, 05 Jul 2006 22:48:30 GMT
    [ http://issues.apache.org/jira/browse/HARMONY-765?page=comments#action_12419353 ] 

Gregory Shimansky commented on HARMONY-765:

Use dos2unix on cl_init.patch before applying it or you will likely get rejects.

> [drlvm] incorrect initialization of default domain in j.l.ClassLoader
> ---------------------------------------------------------------------
>          Key: HARMONY-765
>          URL: http://issues.apache.org/jira/browse/HARMONY-765
>      Project: Harmony
>         Type: Bug

>   Components: VM
>     Reporter: Alexey Varlamov
>     Priority: Blocker
>  Attachments: ClassLoaderTest.java, cl_init.patch
> Latest DRLVM fails to start in presence of "java.security" config file, due to:
> *** Error: exception occured in main Thread constructor.
> java/lang/ExceptionInInitializerError : (null)
> The reason is inappropriate initialization of default domain in j.l.ClassLoader, in static
> Moreover, this initialization deviates from API specification for java.lang.ClassLoader.defineClass():
> "This method assigns a default ProtectionDomain to the newly defined class. The
> ProtectionDomain is effectively granted the same set of permissions returned
> when Policy.getPolicy().getPermissions(new CodeSource(null, null)) is invoked.
> The default domain is created on the first invocation of defineClass, and
> re-used on subsequent invocations."

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message