由于权限错误无法启动 jstatd

cannot start jstatd due to permission error(由于权限错误无法启动 jstatd)

问题描述

我尝试在linux机器上运行jstatd jvm监控工具

I try to run jstatd jvm monitoring tool on linux machine

jboss@hostAddr:/usr/java/jdk1.6.0_18/bin> uname -a
Linux hostAddr 2.6.16.60-0.34-smp #1 SMP Fri Jan 16 14:59:01 UTC 2009 x86_64 x86_64 x86_64 GNU/Linux

使用以下命令:

jstatd -J-Djava.security.policy=~/jstatd.all.policy

jstatd.all.policy 内容

jstatd.all.policy contents

grant codebase "file:${java.home}/../lib/tools.jar" {

   permission java.security.AllPermission;

};

不幸的是，我得到以下输出:

Unfortunately I get following output:

Could not create remote object
access denied (java.util.PropertyPermission java.rmi.server.ignoreSubClasses write)
java.security.AccessControlException: access denied (java.util.PropertyPermission java.rmi.server.ignoreSubClasses write)
        at java.security.AccessControlContext.checkPermission(AccessControlContext.java:323)
        at java.security.AccessController.checkPermission(AccessController.java:546)
        at java.lang.SecurityManager.checkPermission(SecurityManager.java:532)
        at java.lang.System.setProperty(System.java:725)
        at sun.tools.jstatd.Jstatd.main(Jstatd.java:122)

由于某种原因，jstatd 在具有相同命令和策略文件的 Windows 上成功运行.

For some reason jstatd runs successfully on windows with the same command and policy file.

Linux java 版本:

Linux java version:

java version "1.6.0_18"
Java(TM) SE Runtime Environment (build 1.6.0_18-b07)
Java HotSpot(TM) 64-Bit Server VM (build 16.0-b13, mixed mode)

Windows java 版本:

Windows java version:

java version "1.6.0_26"
Java(TM) SE Runtime Environment (build 1.6.0_26-b03)
Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02, mixed mode)

推荐答案

这对我有用:

1. 确保 tools.jar 文件存在并且运行 jstatd 命令的用户有权读取它.

1. Make sure that tools.jar file exists and the user running the jstatd command has permissions to read it.

确保 jstatd.all.policy 中指向 tools.jar 的 URL 正确并声明了协议(在本例中为文件).例如，根据 java.home 变量指向的位置，您可能需要像这样删除路径中的 ../ 部分(我必须这样做):

Make sure that the URL in the jstatd.all.policy that points to the tools.jar is correct and declares the protocol (file in this case). For example, depending on where the java.home variable points to, you may need to remove the ../ part in the path just like this (I had to):

grant codebase "file:${java.home}/lib/tools.jar" {
   permission java.security.AllPermission;
};

jstatd -p 12345 -J-Djava.security.policy=/absolute-path-to/jstatd.all.policy

jstatd -p 12345 -Djava.security.policy=/absolute-path-to/jstatd.all.policy