JDK-6814929 : AttachOnDemand tests fail with "jps -v (stderr): Could not synchronize with target"
  • Type: Bug
  • Component: hotspot
  • Sub-Component: jvmti
  • Affected Version: hs15
  • Priority: P4
  • Status: Resolved
  • Resolution: Not an Issue
  • OS: generic
  • CPU: generic
  • Submitted: 2009-03-09
  • Updated: 2023-12-13
  • Resolved: 2013-11-05
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.
Other
tbdResolved
Related Reports
Relates :  
JDK-6602355 - If a debuggee is waiting for a connection, jps fails with msg: Could not synchronize with target
Relates :  
JDK-6637230 - jps doesn't work for application waiting for direct attach
Description
Observed in nightly testing on 2009.03.07:

New nsk.jvmti failures (from 2009.03.07)
*   nsk/jvmti/AttachOnDemand/attach001
*   nsk/jvmti/AttachOnDemand/attach002
*   nsk/jvmti/AttachOnDemand/attach003
*   nsk/jvmti/AttachOnDemand/attach004
*   nsk/jvmti/AttachOnDemand/attach006
*   nsk/jvmti/AttachOnDemand/attach008
*   nsk/jvmti/AttachOnDemand/attach009
*   nsk/jvmti/AttachOnDemand/attach010
*   nsk/jvmti/AttachOnDemand/attach011
*   nsk/jvmti/AttachOnDemand/attach012
*   nsk/jvmti/AttachOnDemand/attach013
*   nsk/jvmti/AttachOnDemand/attach014
*   nsk/jvmti/AttachOnDemand/attach015
*   nsk/jvmti/AttachOnDemand/attach020
*   nsk/jvmti/AttachOnDemand/attach021
*   nsk/jvmti/AttachOnDemand/attach022
*   nsk/jvmti/AttachOnDemand/attach024
*   nsk/jvmti/AttachOnDemand/attach030
*   nsk/jvmti/AttachOnDemand/attach031
*   nsk/jvmti/AttachOnDemand/attach034
*   nsk/jvmti/AttachOnDemand/attach036
*   nsk/jvmti/AttachOnDemand/attach037
*   nsk/jvmti/AttachOnDemand/attach038
*   nsk/jvmti/AttachOnDemand/attach039
*   nsk/jvmti/AttachOnDemand/attach040
*   nsk/jvmti/AttachOnDemand/attach041
*   nsk/jvmti/AttachOnDemand/attach042
*   nsk/jvmti/AttachOnDemand/attach043
*   nsk/jvmti/AttachOnDemand/attach045
*   nsk/jvmti/AttachOnDemand/attach046
*   nsk/jvmti/AttachOnDemand/attach050
        These tests failed due to the following on Solaris X86 Client
        VM -Xmixed (machine sunjava-64-02):

            jps -v (stderr): Could not synchronize with target
            Exception in thread "main" nsk.share.Failure: Line containing
            'vmsqe.aod.targetAppId=1236492371533' wasn't found in jps output

        Most of these tests are covered by the following unresolved bug:

            6649594 3/3 Intermittent IOExceptions during dynamic attach
                        on linux and solaris

        However, all of the failure modes described in 6649594 are
        related to an IOException of some sort. This failure mode
        doesn't include an IOException so I'll need a new bug.

Here is a link to the analysis page:

http://sqeweb.sfbay/nfs/results/vm/gtee/JDK7/NIGHTLY/VM/2009-03-07/RT_Baseline/vm/solaris-i586/client/mixed/solaris-i586_client_mixed_nsk.jvmti.testlist/analysis.html

I don't remember seeing this failure mode before. I wonder if this
has to do with the OS on the test machine:

% uname -a
SunOS sunjava-64-02 5.11 snv_101b i86pc i386 i86pc
nsk/jvmti/AttachOnDemand/attach002a
Comments
None of the failures matching this bug in 1.8.0 PROMOTION b112 indicates that they are caused by the same issue as in this bugs description. This issue was most likely fixed a long time ago.
05-11-2013