JDK-4331535 : JDI: some VirtualMachine methods do not throw VMDisconnectedException
  • Type: Bug
  • Component: core-svc
  • Sub-Component: debugger
  • Affected Version: 1.4.0
  • Priority: P5
  • Status: Closed
  • Resolution: Duplicate
  • OS: generic
  • CPU: generic
  • Submitted: 2000-04-19
  • Updated: 2001-05-17
  • Resolved: 2001-05-17
Related Reports
Duplicate :  
JDK-4460188 - JDI spec: spec for global RuntimeExceptions inconsistent - centralize it
Description
VirtualMachine does not do the proper check for shutdown.  
For example:
	vm.mirrorOf(true)
can be called after a disconnect.  

See attachment
robert.field@Eng 2000-04-18
Comments
WORK AROUND
11-06-2004
SUGGESTED FIX
11-06-2004
PUBLIC COMMENTS VirtualMachine does not do the proper check for shutdown. For example: vm.mirrorOf(true) can be called after a disconnect.
10-06-2004
EVALUATION Internally a flag is set "shutdown". It is set only on dispose() or exit(), not when the connection goes away. As a result methods on VM which don't call the back-end don't throw the exception. "shutdown" should be set on disconnect (at the same time the VM is removed from the connected list). robert.field@Eng 2000-04-18 However, throwing VMDisconnectedException when we have the info cached is much more likely to break an application than to fix it. We should consider will-not-fix, robert.field@Eng 2001-04-10 4460188 is now the uber bug for exception specification. Closed as a duplicate of 4460188. robert.field@Eng 2001-05-17
10-04-2001