Filed By : JCK team
JDK : java full version "1.6.0-fcs"
JCK : 6a
Platform[s] : all
switch/Mode : default
JCK test owner : http://javaweb.sfbay/jcce/tcks/jck/docs/others/owners.jto
Failed tests:
  vm/jdwp/ObjectReference/ReferringObjects/referringobjects004/referringobjects004.html
  vm/jdwp/ReferenceType/Instances/instances004/instances004.html

Problem description
===================
The JDWP 6.0 specification for ObjectReference.ReferringObjects and ReferenceType.Instances commands at:
  http://javaweb.sfbay/java/re/jdk/6.0/latest/docs/platform/jpda/jdwp/jdwp-protocol.html#JDWP_ObjectReference_ReferringObjects
  http://javaweb.sfbay/java/re/jdk/6.0/latest/docs/platform/jpda/jdwp/jdwp-protocol.html#JDWP_ReferenceType_Instances
states as follows:
  ---Excerpt-from-spec-for-ObjectReference.ReferringObjects---
  Error Data
  ...
  INVALID_OBJECT object is not a known ID
  ---End-of-excerpt---
and
  ---Excerpt-from-spec-for-ReferenceType.Instances---
  Error Data
  ...
  INVALID_OBJECT refType is not a known ID
  ---End-of-excerpt---

However, if command packet which has been sent to debuggee contains unknown objectID/refType (e.g. 0 - null object)
then returned reply packet contains unexpected ILLEGAL_ARGUMENT error code in packet header instead of
INVALID_OBJECT error code. According to JDWP specification the ILLEGAL_ARGUMENT error code is returned only when:
  ---Excerpt-from-spec-for-ObjectReference.ReferringObjects---
  ILLEGAL_ARGUMENT maxReferrers is less than zero.
  ---End-of-excerpt---
and
  ---Excerpt-from-spec-for-ReferenceType.Instances---
  ILLEGAL_ARGUMENT maxInstances is less than zero.
  ---End-of-excerpt---

The following new JCK 6a tests fail due to this issue:
  vm/jdwp/ObjectReference/ReferringObjects/referringobjects004/referringobjects004.html
  vm/jdwp/ReferenceType/Instances/instances004/instances004.html

Please see attached .jtr files for more details.