Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-6637230

jps doesn't work for application waiting for direct attach

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: P2 P2
    • 7
    • 6u3, 7
    • core-svc
    • b132
    • generic, x86
    • generic, windows_xp
    • Verified

      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]

            dcubed Daniel Daugherty
            mrkam Alexander Kuznetcov (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: