JDK-5033431 : SA-JDI: VirtualMachine.version returns empty/null on {-client, class share} mode
  • Type: Bug
  • Component: core-svc
  • Sub-Component: debugger
  • Affected Version: 5.0
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • OS: generic
  • CPU: generic
  • Submitted: 2004-04-17
  • Updated: 2004-04-20
  • Resolved: 2004-04-20
Related Reports
Duplicate :  
Relates :  
Description
The following nsk/sajdi tests fail in {-client, -Xcomp} combinarion.

nsk/sajdi/SADebugServerAttachingConnector/attach/attach002
nsk/sajdi/SAPIDAttachingConnector/attach/attach002

Both the debugger and debuggee are run the same mode. The test fails with error because VirtualMachine.version() returns null/empty. The problem has been seen only on {-client, -Xcomp, share on } mode. Other modes such as {-client, -Xmixed} seem to be fine.

This is *not* related to 5014003. That problem occurs in other modes such as {-client, -Xmixed } as well. 5014003 occurrs because of a change in java.lang.String class and is independent of debugger/debuggee running mode(s).

###@###.### 2004-04-17

I was wrong about -Xcomp in above description. It should say the problem is reproduced in {-client, class share on } mode.


###@###.### 2004-04-17

Comments
EVALUATION The root cause of this problem is same as that of 5029618 - jinfo -sysprops throws NPE when used against a debuggee that runs with class sharing turned on. The bug seemed to persist because the modified sa-jdi.jar [and libsaproc.so] were not used in nightly testing. I am closing this as duplicate of 5029618. A run of SA/JDI NSK in {solaris, sparc, -client, -Xshare:on} mode has successfully completed without this version problem. With class sharing, perm gen. limits checking has to include shared heap as well. This was the fix for 5029618. ###@###.### 2004-04-20
20-04-2004