JDK-6399729 : jconsole cannot attach services via remote desktop protocol
  • Type: Bug
  • Component: tools
  • Sub-Component: jconsole
  • Affected Version: 6
  • Priority: P3
  • Status: Resolved
  • Resolution: Won't Fix
  • OS: windows_2003
  • CPU: x86
  • Submitted: 2006-03-16
  • Updated: 2023-12-14
  • Resolved: 2013-07-30
Description
FULL PRODUCT VERSION :
1.6.0-beta2-b75

ADDITIONAL OS VERSION INFORMATION :
Windows 2003 Server [Version 5.2.3790]

EXTRA RELEVANT SYSTEM CONFIGURATION :
Windows 2003 server was accessed via remote desktop protocol from a windows XP machine.

A DESCRIPTION OF THE PROBLEM :
JConsole does not attach any services when using remote desktop protocol. JConsole "Create a new connection" window show the service name and PID with gray colored message. No error messages were shown.

JConsole could attach the same services with local login.

REPRODUCIBILITY :
This bug can be reproduced always.
Comments
It's a bug on an old JDK (6) running on old operating system, and it's likely a user error. Can't be reproduced on Windows 7.
30-07-2013
Impact=High, not able to use GUI at all Likelihood=Low, only happens if using Windows remote desktop Workaournd=Medium, use other technology, i.e. VNC HLM => P3
30-07-2013
EVALUATION From the attached remote-login screenshot, the management agent is not enabled. It means that it's a process that running on pre-Mustang JDK (Tiger or 1.4.2) that doesn't support attach-on-demand. I suspect the service that the submitter attaches via remote desktop is not running on Mustang. Could the submitter provide the following information via rdesktop as well as the local attach: 1) jconsole -debug <pid> 2) jps -l 3) jps -snap <pid> This should provide the details to confirm if the process supports attach-on-demand or not.
13-06-2006
EVALUATION -- Also, can the submitter try "jconsole -debug <pid>" and post the output as a comment on the bug.
27-04-2006
EVALUATION Could be related to 6355952
20-03-2006