JDK-4422587 : JCK13a: Three vm/instr/new tests fail with java.lang.InstantiationError
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 1.4.0
  • Priority: P2
  • Status: Closed
  • Resolution: Duplicate
  • OS:
    generic,linux,windows_95,windows_2000 generic,linux,windows_95,windows_2000
  • CPU: x86,sparc
  • Submitted: 2001-03-07
  • Updated: 2001-03-30
  • Resolved: 2001-03-30
Related Reports
Duplicate :  
Description

Name: iaR10016			Date: 03/07/2001



Failing Test:
=============
vm/instr/new/new002/new00201m1/new00201m1.html
vm/instr/new/new002/new00202m1/new00202m1.html
vm/instr/new/new007/new00702m1/new00702m1.html

JCK :
=====
JCK1.3a

Test source location:
====================
/net/jdk/export/disk8/local.java/jck1.3a/JCK-runtime-13a/tests/vm/instr/new/new002/new00201m1/new00201m1.java
/net/jdk/export/disk8/local.java/jck1.3a/JCK-runtime-13a/tests/vm/instr/new/new002/new00202m1/new00202m1.java
/net/jdk/export/disk8/local.java/jck1.3a/JCK-runtime-13a/tests/vm/instr/new/new007/new00702m1/new00702m1.java

Platforms:
=============
Windows 2000
Windows 98
Windows 95
Windows ME
Redhat Linux 6.2
Caldera OpenLinux

JDK, switches Info:
===================
java version "1.4.0-beta"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-beta-b54)
Java HotSpot(TM) Client VM (build 1.4beta-B54, mixed mode)

The bug is reproducible with all switches

jtr file location:
==================
/net/jtgb4u4c.eng/export/sail7/JavaWebServer1.1.3/public_html/QA/merlin/b54/jck13a/linux/redhat6.2_smp_kde_client_comp_linux-5/workDir/vm/instr/new/new002/new00201m1/new00201m1.jtr
/net/jtgb4u4c.eng/export/sail7/JavaWebServer1.1.3/public_html/QA/merlin/b54/jck13a/linux/redhat6.2_smp_kde_client_comp_linux-5/workDir/vm/instr/new/new002/new00202m1/new00202m1.jtr
/net/jtgb4u4c.eng/export/sail7/JavaWebServer1.1.3/public_html/QA/merlin/b54/jck13a/linux/redhat6.2_smp_kde_client_comp_linux-5/workDir/vm/instr/new/new007/new00702m1/new00702m1.jtr

How to reproduce:
====================
#!/bin/sh

JAVA_HOME=/usr/local/java/jdk1.4/linux-i386

JCK=/net/jdk/export/disk8/local.java/jck1.3a

CLASSPATH=$JCK/classes:$JCK/javatest.jar
export CLASSPATH

LD_LIBRARY_PATH=/net/linux-15/export/home/jck1.3a/lib
export LD_LIBRARY_PATH

executeClass="javasoft.sqe.tests.vm.instr.newX.new002.new00201m1.new00201m1"

$JAVA_HOME/bin/java -version

$JAVA_HOME/bin/java ${executeClass}
RESULT="$?"

if [ $RESULT = 95 ]; then
 echo Test passed
elif [ $RESULT = 97 ]; then
 echo Test failed
else
 echo Result is $RESULT
fi

Test output:
=============
java version "1.4.0-beta"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-beta-b54)
Java HotSpot(TM) Client VM (build 1.4beta-B54, mixed mode)

Unexpected exception on runMethod.invoke() invocation: java.lang.InstantiationError: javasoft.sqe.tests.vm.instr.newX.new002.new00201m1._new00201m1n
Test failed

Specific Machine Info:
=====================
Hostname: linux-22

Additional JCK related info:
============================
URL to find JCK test owners: http://javaweb.eng/jck/usr/owners.jto
JCK FAQ: http://javaweb.eng/jck/usr/ConformanceTesting/JCKconformanceFaq.html

======================================================================

Comments
EVALUATION vm/instr/new/new002/new00201m1/new00201m1.html From JVM Spec: InstantiationError: A symbolic reference has been encountered that is used in a class instance creation expression, but an instance cannot be created because the reference turns out to refer to an interface or to an abstract class. This can occur, for example, if a class that is originally not abstract is changed to be abstract after another class that refers to the class in question has been compiled. [Test is wrong] vm/instr/new/new002/new00202m1/new00202m1.html InstantiationError: A symbolic reference has been encountered that is used in a class instance creation expression, but an instance cannot be created because the reference turns out to refer to an interface or to an abstract class. This can occur, for example, if a class that is originally not abstract is changed to be abstract after another class that refers to the class in question has been compiled. [Test is wrong] vm/instr/new/new007/new00702m1/new00702m1.html InstantiationError: A symbolic reference has been encountered that is used in a class instance creation expression, but an instance cannot be created because the reference turns out to refer to an interface or to an abstract class. This can occur, for example, if a class that is originally not abstract is changed to be abstract after another class that refers to the class in question has been compiled. [Test is wrong] robertg@east 2001-03-26 All listed tests are valid. These tests are failing due to incorrect behavior of java.lang.reflect.Method.invoke() method (bug report #4428861). Therefore this bug may be closed as duplicate of 4428861.
11-06-2004