我在带有 Java 1.6 u 20 的 Windows Server 2003 下将 GlassFish 3.0.1 作为 Windows 服务运行，总体上我很满意。
我希望能够在此 JVM 上使用 VisualVM 并使用 无法使用 JConsole 与作为 Windows 服务运行的 Tomcat 作为起点，但以
PsTools\PsExec.exe -i -s "C:\Program Files\Java\jdk1.6.0_20\bin\jvisualvm.exe"
SYSTEM 用户身份在任务管理器中显示 jvisualvm.exe 和 nbexec.exe 进程的结果 开始但我没有看到程序中的任何 GUI，就像我自己手动运行它时看到的那样。我从 Windows 7 使用远程桌面登录，以防有任何影响。
其他有趣的点：
at 10:55 /interactive cmd.exe
报告已添加新作业，但在 10.55 时未打开 CMD 窗口。
如何将 VisualVM 注册为服务的描述报告服务已启动，但没有显示 GUI。 http://blogs.oracle.com/nbprofiler/entry/monitoring_java_processes_running_as
有人得到过吗这可以在 Windows Server 2003 下运行吗？
I am running GlassFish 3.0.1 as a windows service under Windows Server 2003 with Java 1.6 u 20, and am generally happy.
I would like to be able to use VisualVM on this JVM and used Unable to use JConsole with Tomcat running as windows service as a starting point, but starting with
PsTools\PsExec.exe -i -s "C:\Program Files\Java\jdk1.6.0_20\bin\jvisualvm.exe"
results in a jvisualvm.exe and a nbexec.exe process showing up in Task Manager with SYSTEM as the user but I do not see any GUI from the program as I do when I run it manually as myself. I am logged in with Remote Desktop from Windows 7 in case that makes any difference.
Other interesting points:
at 10:55 /interactive cmd.exe
reports a new job has been added, but does not open a CMD window at 10.55.
The description of how to register VisualVM as a service reports the service to start but no GUI shows up. http://blogs.oracle.com/nbprofiler/entry/monitoring_java_processes_running_as
Have anybody gotten this to run under Windows Server 2003?
发布评论
评论（1）
我能够让它工作的方法是确保您远程桌面到服务器的“控制台”会话。
简而言之，当您打开 mstsc.exe 时，将文本“/admin”附加到您尝试连接的计算机名称。例如，如果您尝试连接到名为“FOO”的服务器，则在 mstsc.exe 的计算机名文本框中输入“FOO /admin”。
连接并登录服务器后，您可以执行 PsExec 命令。然后，您应该会看到 Visual VM 以及您尝试连接的 GlassFish 进程。
有关在 Windows 中使用远程桌面连接到控制台会话的详细信息，请查看“如何连接到控制台”部分 http://support.microsoft.com/kb/278845。
此外，对于那些寻找 PsExec.exe 的人，您可以从 Microsoft 的 PsTools 包中获取它，网址为 technet.microsoft.com/en-us/sysinternals/bb897553.aspx。
The way I'm able to get this to work is to make sure that you remote desktop to the server's "console" session.
Simply put, when you open mstsc.exe append the text " /admin" to the computer name you are trying to connect to. For instance, if you were trying to connect to a server called "FOO", then in the Computer name text box in mstsc.exe, you would enter "FOO /admin".
After connecting and logging in to the server, you can execute your PsExec command. You should then see Visual VM with the GlassFish process you are trying to connect to.
For more info about connecting to the console session with remote desktop in Windows, have a look at the "How to Connect to the Console" section http://support.microsoft.com/kb/278845.
Also, for those looking for PsExec.exe, you can get it from the PsTools package from Microsoft at technet.microsoft.com/en-us/sysinternals/bb897553.aspx.