geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ying Tang (JIRA)" <j...@apache.org>
Subject [jira] Commented: (GERONIMO-4534) Can't secure connect to JMX with JConsole.
Date Tue, 10 Feb 2009 08:32:59 GMT

    [ https://issues.apache.org/jira/browse/GERONIMO-4534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672201#action_12672201
] 

Ying Tang commented on GERONIMO-4534:
-------------------------------------

Thanks. It also works well with WASCE 2.1.1.1 and  WASCE 2.1.1.2.
I found we cannot shutdown the server via the "shutdown" command after we quit JConsole:
Failed to retrieve the RMIserver stub: javax.naming.NameNotFoundException: JMXConnector.

> Can't secure connect to JMX with JConsole.
> ------------------------------------------
>
>                 Key: GERONIMO-4534
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4534
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: management
>    Affects Versions: 2.1.4, 2.2
>         Environment: Windows XP 
> Sun JDK 1.5
> geronimo_tomcat6_2.1.4_snapshot/20090209/
>            Reporter: Shawn Jiang
>
> I'm trying to use jconsole to securely connect to the JMX server of geronimo 2.1.4 snapshot
according to the guide here:
> http://cewiki.cn.ibm.com:7080/confluence/display/V21Docs/Working+with+the+secure+JMX+server
> * 1, Change the config.xml and start the server.
> * 2, use "jconsole -J-Djavax.net.ssl.keyStore=%GERONMO_HOME%\var\security\keystores\geronimo-default
-J-Djavax.net.ssl.keyStorePassword=secret -J-Djavax.net.ssl.trustStore=%GERONMO_HOME%\var\security\keystores\geronimo-default
-J-Djavax.net.ssl.trustStorePassword=secret " start the jconsole.
> * 3, in the jconsole interface->advanced, input:
> JMX URL:   service:jmx:rmi:///jndi/rmi://localhost:1099/JMXSecureConnector
> user name: system
> password: manager
> * 4, click the connect button.
> expected result: could connect to the JMX server.
> actual result:  CAN NOT connect to the JMX server.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message