[
http://issues.apache.org/jira/browse/GERONIMO-848?page=comments#action_12317541
]
Aaron Mulder commented on GERONIMO-848:
---------------------------------------
Here's the code (from DeploymentFactoryImpl):
if (uri.startsWith("jmx")) {
Map environment = new HashMap();
String[] credentials = new String[]{username, password};
environment.put(JMXConnector.CREDENTIALS, credentials);
try {
JMXServiceURL address = new JMXServiceURL("service:" + uri);
JMXConnector jmxConnector =
JMXConnectorFactory.connect(address, environment);
So I think it's a problem with the underlying JMX code, or else we're not
constructing the URL properly (again, our URL is
jmx:rmi://host:port/jndi/rmi:/JMXConnector which becomes
service:jmx:rmi://host:port/jndi/rmi:/JMXConnector)
I don't know who's responsible for the code that handles that URL
> Deployer ignores Geronimo URL host/port
> ---------------------------------------
>
> Key: GERONIMO-848
> URL: http://issues.apache.org/jira/browse/GERONIMO-848
> Project: Geronimo
> Type: Bug
> Components: deployment
> Versions: 1.0-M4
> Reporter: Aaron Mulder
> Fix For: 1.0-M5
>
> When the deployer connects to a server, it uses a URL of the form:
> deployer:geronimo:jmx:rmi://host:port/jndi/rmi:/JMXConnector
> Under the covers, this strips off the beginning and uses a connection of the
> form:
> jmx:rmi://host:port/jndi/rmi:/JMXConnector
> However, no matter what you use as the host and port, it connects to the
> standard port on localhost. It should actually attempt to connect to the
> host and port specified and give an error if they are not valid.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
