Java Solaris Communities Sun Store Join SDN My Profile Why Join?
 
Bug Database
Bug Detail
Quick Lists
Top 25 Bugs
Top 25 RFE's
Recently Closed Bugs
Printable Page Printable Page


Bug Database
Bug ID: 6763006
Votes 0
Synopsis JDK HotSpot builds not using SS12 / VM doesn't find classes from JDK/lib/tools.jar in -Xcomp mode
Category java:build
Reported Against b35
Release Fixed 7(b39)
State 10-Fix Delivered, bug
Priority: 2-High
Related Bugs 5108146
Submit Date 23-OCT-2008
Description
Since JDK7b35 JDI/SAJDI tests fail with solaris-amd64 in -Xcomp mode because of VM can't find classes from JDK/lib/tools.jar. This bug reproduces only with product VM (doesn't reproduce with fastdebug).

Event the simplest test fails:

// Test.java
import com.sun.jdi.request.EventRequest;

public class Test {

    public static void main(String[] args) throws Exception {
        Object obj = new Object();
        System.out.println(obj instanceof EventRequest);
    }
}


/net/vmsqe.russia/export/jdk/7/build/latest/solaris-amd64/bin/java -cp .:/net/vmsqe.russia/export/jdk/7/build/latest/solaris-amd64/lib/tools.jar -d64 -Xcomp Test
Exception in thread "main" java.lang.NoClassDefFoundError: com/sun/jdi/request/EventRequest
        at Test.main(Test.java:7)
Caused by: java.lang.ClassNotFoundException: com.sun.jdi.request.EventRequest
        at java.net.URLClassLoader$1.run(URLClassLoader.java:220)
        at java.net.URLClassLoader$1.run(URLClassLoader.java:209)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.net.URLClassLoader.findClass(URLClassLoader.java:208)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:325)
        at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:294)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:270)
        at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:338)

Failure can be reproduced for example on vmsqe-amd-06.russia.
Posted Date : 2008-10-23 13:22:14.0
Work Around
N/A
Evaluation
The JDK7 builds are being mistakenly built with the SS11 compilers, causing a native compiler problem with javaCalls.o.  The problem disappears if the correct SS12 compiler is used.
Posted Date : 2008-10-27 16:38:51.0

The COMPILER_PATH was pointing to SS12.  The overall PATH was still pointing to SS11 and that has been updated.
Posted Date : 2008-10-27 17:38:29.0
Comments
  
  Include a link with my name & email   


PLEASE NOTE: JDK6 is formerly known as Project Mustang