You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Pavel Pervov (JIRA)" <ji...@apache.org> on 2007/05/22 14:25:16 UTC

[jira] Commented: (HARMONY-3891) [drlvm][thread] null Thread.currentThread in custom system classloader constructor

    [ https://issues.apache.org/jira/browse/HARMONY-3891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12497843 ] 

Pavel Pervov commented on HARMONY-3891:
---------------------------------------

The problem is in kernel classes. java/lang/Thread constructor makes call to ClassLoader.getSystemClassLoader. Since this test overloads system class loader and calls to Thread.currentThread()'s methods, this test produces NPE.

getSystemClassLoader should not be called before main thread is created.

Will try to elaborate some sane way to untie all these...

> [drlvm][thread] null Thread.currentThread in custom system classloader constructor
> ----------------------------------------------------------------------------------
>
>                 Key: HARMONY-3891
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3891
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>         Environment: Windows, Linux
>            Reporter: Sergey Salishev
>         Attachments: ClassLoader1.java
>
>
> When running the attached test case with 
> java -Djava.system.class.loader=ClassLoader1 bla
> the Thread.currentThread returns unexpected null value

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