jboss和mission control连接的问题

最近再使用jrockit的mission control进行jboss的j2ee的性能优化，但是只要一点就报错，错误为Failed to start the management agent. Note that the management agent requires that you either explicitly disable security or that you configure and enable security. Please see the documentation for details.

就是说要对jdk的security进行显示的设置才可以进行连接，:-)

在网上找了一下，发现oracle的官方文档里面居然有说明，:-)  摘抄出来，将jboss的启动脚本的java_path后面添加上-Xmanagement:ssl=false,authenticate=false 设置就可以了 

 

附：

-Xmanagement

This option starts the JRockit JVM concurrently with the management server and allows you to either enable and configure or explicitly disable security features such as SSL encryption and authentication.

Operation

Format: -Xmanagement[:<argument1>=<value1>[,<argument2>=<value2>]]

where argumentn and valuen is as defined in Table 2-5.

Table 2-5 -Xmanagement Arguments

Argument	Description
autodiscovery=<true|false>	Enables or disables autodiscovery, which allows Oracle JRockit Mission Control to automatically discover running JRockit JVM instances through the multicast-based JRockit Discovery Protocol. Valid with JRockit JVM 5.0.
ssl=<true|false>	Enables or disables SSL encryption. Valid with JRockit JVM 5.0.
authenticate=<true|false>	Enables or disables authentication. Valid with JRockit JVM 5.0.
port= <portNumber>	Identifies the port that the management server will open for remote access. Valid with JRockit JVM 5.0.
class=	This option loads the class and causes its empty constructor to be called early in JVM startup. From the constructor, a new thread is then started, from which your management client is run. Further arguments cannot be given to -Xmanagement after the class argument.

For Example:

• java -Xmanagement:ssl=false,authenticate=false myApplication

  Disables SSL encryption and authentication.

• java -Xmanagement:autodiscovery=true myApplication

  Enables autodiscovery.

• java -Xmanagagement:port=1234 myApplication

  Tells the management server to open port 1234.

The implementation of this option in JRockit JVM R27.1.0 represents a change from previous versions of the product. In past versions, this option enabled the management server running:

• A JMX agent (for JRockit JVM versions based on J2SE 5.0).
• Oracle’s proprietary RMP protocol (for JRockit JVM versions based on J2SE 1.4.2).

The original RMP implementation had no security features. JRockit JVM 5.0 contains new security features—authentication and SSL encryption—that were introduced in J2SE 5.0, but similar security features were not enabled in the JRockit JVM 1.4.2.

Due to the security risks and the mission-critical nature of most JRockit JVM deployments, the new default behavior of the JRockit JVM requires that you either disable security explicitly or configure and enable security. If you don’t take these steps, the management server will not open a port for remote access and may cause the JVM startup to halt with an error message concerning the security configuration.

Specifying -Xmanagement also enables a local in-memory agent to improve the user experience from a developer perspective. For example, a developer running a WLS instance on JRockit JVM on a one machine can specify – Xmanagement to enable the local in-memory agent to connect to it from an Oracle JRockit Mission Control Client on another machine. On the other hand, the developer would not need to specify – Xmanagement to get local access from JRockit Mission Control: the in-memory agent is always accessible locally. Thus, if you have a number of JRockit JVM instances running on your machine and you start a JRockit Mission Control Client, it will automatically discover and allow access to those JVMs. Security is enforced by only allowing this type of local access if the JRockit JVM instance and the JRockit Mission Control Client are being run by the same user. Note that this will only work if the monitored JRockit JVM is R27.1 and later.

To enable the management agent without security you must now specify that SSL and authentication should be disabled. Also, the JMX server port must now be specified explicitly with the JRockit JVM 5.0.

For maximum usability, you should also enable the autodiscovery mechanism, which allows JRockit Mission Control to automatically discover running JRockit JVM instances through the multicast based JRockit Discovery Protocol. Note that this will normally only work on the local subnet.

To limit the number of RMP connections running at the same time, you can set -Djrockit.managementserver.maxconnect.