JDK-6637230 : jps doesn't work for application waiting for direct attach
  • Type: Bug
  • Component: core-svc
  • Sub-Component: tools
  • Affected Version: 6u3,7
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: generic,windows_xp
  • CPU: generic,x86
  • Submitted: 2007-12-04
  • Updated: 2016-11-29
  • Resolved: 2011-03-08
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 7
7 b132Fixed
Related Reports
Duplicate :  
JDK-6602355 - If a debuggee is waiting for a connection, jps fails with msg: Could not synchronize with target
Duplicate :  
JDK-6986875 - TEST failed: sun/tools/jps/jps-Vvml.sh
Relates :  
JDK-6814929 - AttachOnDemand tests fail with "jps -v (stderr): Could not synchronize with target"
Relates :  
JDK-8170487 - jvmstat fails to send updates to listener on unchecked exception
Description
http://www.netbeans.org/issues/show_bug.cgi?id=114264

Steps to reproduce:
- Start any application with direct attach options for NetBeans Profiler, do not perform attach
  - Download NetBeans 6.0
  - Select Profile > Attach Profiler from main menu
  - Follow wizard steps to run application with the command for local direct attach:
    java -agentpath:"C:\Program Files\NetBeans 6.0 Beta 1\profiler2\lib\deployed\jdk15\windows\profilerinterface.dll=\"C:\Program Files\NetBeans 6.0 Beta 1\profiler2\lib\"",5140 -jar yourapp.jar    
  - Do not perform attach
- Run jps
- RESULT: "Could not synchronize with target" message
6602355 was closed as duplicate of this bug. However,
that no longer causes the fail_list entries to follow
so I'm copying the relevant entries from 6602355:

This failure mode has been seen in nightly testing. Here is
my analysis report entry:

New MISC_REGRESSION failures (from 2007.11.22)
    sun/tools/jps/jps-lm.sh
    sun/tools/jps/jps-l_2.sh
    sun/tools/jps/jps-m_2.sh
    sun/tools/jps/jps-Vm_2.sh
    sun/tools/jps/jps-Vvml.sh
    sun/tools/jps/jps-Vvml_2.sh
    sun/tools/jps/jps-V_2.sh
        These tests failed due to "Could not synchronize with target" on
        Win32 Client VM (machine vm-8450r-3).

        Update: Swamy believes these failures are due to problems with
            the test machine.

        Update: Swamy found the following existing bug:
            6602355 4/4 If a debuggee is waiting for a connection, jps
                        fails with msg: Could not synchronize with target

        Update: Swamy verified that the failures on vm-8450r-3 are due
            to 6602355.

6602355 Entry 2 daniel.daugherty [2007-12-10 15:53]
Here is another analysis report entry:

New MISC_REGRESSION failures (from 2007.11.28)
    sun/tools/jps/jps-Defaults.sh
    sun/tools/jps/jps-l_1.sh
*   sun/tools/jps/jps-m.sh
    sun/tools/jps/jps-Vm_2.sh
        These tests failed due to "Could not synchronize with target"
        on Win-AMD64 Server VM (machine vm-x2100-01). These failures
        are an occurrence of the following bug:

            6602355 4/4 If a debuggee is waiting for a connection, jps
                        fails with msg: Could not synchronize with target

6602355 Entry 3 daniel.daugherty [2007-12-10 21:12]
Here is another analysis report entry:

New MISC_REGRESSION failures (from 2007.12.06)
*   sun/tools/jps/jps-Vvm.sh
*   sun/tools/jps/jps-v_1.sh
*   sun/tools/jps/jps-vm_1.sh
        These tests failed due to "Could not synchronize with target"
        on Win32 Server VM (machine colfax005). These failures are an
        occurrence of the following bug:

            6602355 4/4 If a debuggee is waiting for a connection, jps
                        fails with msg: Could not synchronize with target

6602355 Entry 4 daniel.daugherty [2007-12-10 22:23]
Comments
EVALUATION Changeset: b04e86b3e27e Author: dcubed Date: 2011-02-14 09:31 -0800 URL: http://hg.openjdk.java.net/jdk7/tl/jdk/rev/b04e86b3e27e 6637230: 2/3 jps doesn't work for application waiting for direct attach Summary: Properly handle exceptions thrown when querying a monitored VM. Reviewed-by: dsamersoff, swamyv ! src/share/classes/sun/tools/jps/Jps.java
14-02-2011
SUGGESTED FIX Please see the attached 6637230-webrev-cr1.tgz for the proposed fix that was sent out for code review (round 1).
14-02-2011
SUGGESTED FIX Please see attached 6637230-webrev-cr0.tgz for the proposed fix that was sent out for code review (round 0).
12-02-2011
EVALUATION Need to do a little more than ignore the MonitorException. There is already good exception handling code in jps for the initial call to monitoredHost.getMonitoredVm(). The other calls that gather info just need to make use of the existing exception handling code (with tweaks): MonitoredVmUtil.mainClass(vm, arguments.showLongPaths()) MonitoredVmUtil.mainArgs(vm) MonitoredVmUtil.jvmArgs(vm) MonitoredVmUtil.jvmFlags(vm) monitoredHost.detach(vm) The "Could not synchronize with target" failure mode happens during the call to MonitoredVmUtil.mainClass().
03-02-2011
EVALUATION Ignore monitored host exception for vms which it can not access it.
08-01-2008
EVALUATION I think this is a duplicate of the following bug: 6602355 4/4 If a debuggee is waiting for a connection, jps fails with msg: Could not synchronize with target I'm also moving this bug to java/java/serviceability.
07-12-2007