Dave,

Yes you are correct. Forgot about that :-)

A manual change is required to the geronimo-1.0\var\config\config.xml file.

The section:

       <gbean name="JMXConnector">
<attribute name="url">service:jmx:rmi://0.0.0.0/jndi/rmi:/JMXConnector</attribute>
       </gbean>

Needs to be replaced with (note that both the value for the name attribute and the url have changed):

   <gbean name="JMXService">
<attribute name="url">service:jmx:rmi://0.0.0.0/jndi/rmi://localhost:1099/JMXConnector</attribute>
   </gbean>

Change port 1099 in the url attribute for the JMXService GBean with the value you specified in the the port attribute for the RMIRegistry GBean.

FYI, there is a related known problem where the RMIConnection and RMIServer is bound to is not listed at startup - GERONIMO-1349 - Missing Ports in Startup Port List.

The following are some example JMXService urls (the url above uses the format in example 3 below, but you may want to change the format if you need to use JMX through a firewall or feel more comfortable with listening ports numbers being predictable):

Example 1) service:jmx:rmi://0.0.0.0:9999/jndi/rmi://0.0.0.0:1099/JMXConnector

The RMI Connector Server will be bound to the RMIRegistry running on port 1099 and the RMIConnection and RMIServer remote objects will be bound to port 9999, listening on any IP addresses (0.0.0.0).

Example 2) service:jmx:rmi:///jndi/rmi://0.0.0.0:1099/JMXConnector

The RMI Connector Server will be bound to the RMIRegistry running on port 1099 and the RMIConnection and RMIServer remote objects will be bound to a random port, on the localhost. Since the port is random it isn't firewall friendly.

Example 3) service:jmx:rmi://0.0.0.0/jndi/rmi://0.0.0.0:1099/JMXConnector

The RMI Connector Server will be bound to the RMIRegistry running on port 1099 and the RMIConnection and RMIServer remote objects will be bound to a random port, listening on any IP addresses (0.0.0.0). Since the port is random it isn't firewall friendly.

Regards,

John

Dave Colasurdo wrote:
John,

Isn't there a manual workaround needed in G 1.0 for the JMXConnector (RMI port) as mentioned in GERONIMO-1352?

-Dave-

John Sisson wrote:
Cristian Roldan wrote:

Hi All,
Does Geronimo support installing several instances on the same server ? each instance running independently . If possible, how can I do it ... Thanks

------------------------------------------------------------------------
*1GB gratis*, Antivirus y Antispam
Correo Yahoo!, el mejor correo web del mundo
Abrí tu cuenta aquí <http://login.yahoo.com/config/mail?.intl=ar>

You should be able to install Geronimo in different locations for each instance and it should just be a matter of changing the ports that Geronimo listens on in the geronimo\var\config\config.xml file. Make sure you don't edit this file while geronimo is running or you will lose your changes.

After changing the file, start Geronimo and the startup output sent to the terminal should summarize the ports that Geronimo is listening on. The GUI installer planned for the 1.0.1 release should make it even easier to customize port numbers if you don't like having to edit the config.xml file.

The plan for future releases is to allow Geronimo to share static files such as jar files, startup scripts etc across instances and therefore each instance will just have its own copy of instance specific files (e.g. the files under the geronimo\var directory).

Regards,

John





Reply via email to