You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Vasily Zakharov (JIRA)" <ji...@apache.org> on 2006/12/12 18:44:25 UTC
[jira] Updated: (HARMONY-2650) [drlvm][exception] massive boot
class loading causes uncaught ClassNotFoundException
[ http://issues.apache.org/jira/browse/HARMONY-2650?page=all ]
Vasily Zakharov updated HARMONY-2650:
-------------------------------------
Attachment: Test.java
Test to reproduce the problem
> [drlvm][exception] massive boot class loading causes uncaught ClassNotFoundException
> ------------------------------------------------------------------------------------
>
> Key: HARMONY-2650
> URL: http://issues.apache.org/jira/browse/HARMONY-2650
> Project: Harmony
> Issue Type: Bug
> Components: DRLVM
> Reporter: Vladimir Beliaev
> Priority: Minor
> Attachments: Test.java
>
>
> I've double checked the results of running test described in http://issues.apache.org/jira/browse/HARMONY-2615.
> Unhandled ClassNotFoundException happens while this test running in spite of try { ... } catch (Throwable e) {} wrapping.
> I've created this JIRA to let working on this current issue regardless whether the test is integrated to any suite or not.
> Please take the test from http://issues.apache.org/jira/browse/HARMONY-2615.
> Part of test output (which shows issue) for Windows/IA32 and Linux/IA32 is:
> .... org.mmtk.plan.Plan
> java.lang.ClassNotFoundException: null.Factory
> at java.lang.Class.forName(Unknown Source)
> at java.lang.Class.forName(Unknown Source)
> at org.mmtk.vm.VM.<clinit>(Unknown Source)
> at org.mmtk.utility.Constants.<clinit>(Unknown Source)
> at org.mmtk.plan.Plan.<clinit>(Unknown Source)
> at java.lang.VMClassRegistry.initializeClass(Native Method)
> at java.lang.Class.forName(Unknown Source)
> at java.lang.Class.forName(Unknown Source)
> at CrashTestBCP.load(CrashTestBCP.java:75)
> at CrashTestBCP.main(CrashTestBCP.java:98)
> Thanks
> Vladimir
--
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