You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Alexey Varlamov (JIRA)" <ji...@apache.org> on 2006/07/05 11:45:29 UTC
[jira] Created: (HARMONY-765) [drlvm] incorrect initialization of
default domain in j.l.ClassLoader
[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
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 block.
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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Assigned: (HARMONY-765) [drlvm] incorrect initialization of
default domain in j.l.ClassLoader
Posted by "Mark Hindess (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HARMONY-765?page=all ]
Mark Hindess reassigned HARMONY-765:
------------------------------------
Assign To: Mark Hindess
> [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
> Assignee: Mark Hindess
> 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 block.
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (HARMONY-765) [drlvm] incorrect initialization of
default domain in j.l.ClassLoader
Posted by "Alexey Varlamov (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HARMONY-765?page=all ]
Alexey Varlamov updated HARMONY-765:
------------------------------------
Attachment: ClassLoaderTest.java
The test case for checking default domain properties. I'm unsure there it should go - which package and module (seems there are no any tests in the luni-kernel).
> [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 block.
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (HARMONY-765) [drlvm] incorrect initialization of
default domain in j.l.ClassLoader
Posted by "Alexey Varlamov (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HARMONY-765?page=all ]
Alexey Varlamov updated HARMONY-765:
------------------------------------
Attachment: cl_init.patch
The fix for this issue.
> [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 block.
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (HARMONY-765) [drlvm] incorrect initialization of
default domain in j.l.ClassLoader
Posted by "Mark Hindess (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HARMONY-765?page=comments#action_12419530 ]
Mark Hindess commented on HARMONY-765:
--------------------------------------
Applied the patch in r419556. Can you confirm that this is as expected?
Can you also raise the issue of luni-kernel tests on the dev list with reference to this JIRA as an example of a VM-independent test? If people think it makes sense to add these to classlib (as I do), then I'll add it. Thanks.
> [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
> Assignee: Mark Hindess
> 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 block.
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (HARMONY-765) [drlvm] incorrect initialization of
default domain in j.l.ClassLoader
Posted by "Gregory Shimansky (JIRA)" <ji...@apache.org>.
[ 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 block.
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Closed: (HARMONY-765) [drlvm] incorrect initialization of
default domain in j.l.ClassLoader
Posted by "Mark Hindess (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HARMONY-765?page=all ]
Mark Hindess closed HARMONY-765:
--------------------------------
Resolution: Fixed
Test added to classlib in r419989.
> [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
> Assignee: Mark Hindess
> 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 block.
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (HARMONY-765) [drlvm] incorrect initialization of
default domain in j.l.ClassLoader
Posted by "Alexey Varlamov (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HARMONY-765?page=comments#action_12419649 ]
Alexey Varlamov commented on HARMONY-765:
-----------------------------------------
Verified.
Also started a new thread http://thread.gmane.org/gmane.comp.java.harmony.devel/9812/
> [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
> Assignee: Mark Hindess
> 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 block.
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (HARMONY-765) [drlvm] incorrect initialization of
default domain in j.l.ClassLoader
Posted by "Alexey Varlamov (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/HARMONY-765?page=comments#action_12419250 ]
Alexey Varlamov commented on HARMONY-765:
-----------------------------------------
Please note, there is subtle difference between ProtectionDomains constructors, assigning static and dynamic permissions set. To support dynamic security policy, the default domain must be per-instance (not static) field of ClassLoader.
> [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 block.
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira