Re: JMX JRMP rmi registry port configuration

2004-01-08 Thread Kevin Pfarr
The option mx.jrmpPort is used for registering the JRMPAdaptor to the 
NamingService, by setting the PROVIDER_URL.  When the NamingService is 
regeristered it creates the rmi registry whiCh defaults to 1099.

The code below will show what I mean about setting the port on the rmi 
registry.  The code below is from the class org.apache.jk.common.JkMX.


jrmpServerName = new ObjectName("Naming:name=rmiregistry");
mserver.createMBean("mx4j.tools.naming.NamingService", jrmpServerName, 
null);

// new line to set the rmi registry port to 1199
server.setAttribute(naming, new Attribute("Port", new Integer("1199")));
mserver.invoke(jrmpServerName, "start", null, null);
log.info( "Creating " + jrmpServerName );

-Kevin

Bill Barker wrote:
- Original Message - 
From: "Kevin Pfarr" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, January 08, 2004 2:55 PM
Subject: JMX JRMP rmi registry port configuration



When JMX is enabled, in the jk2.properties file, and configured to use 
the MX4J JRMP interal adapter, a rmi registry is created and bound to 
the default port of 1099.  If there is another application using that 
port and bind expection is thrown and the adaptor is never enabled.

A configuration option for the rmi registry port would sovle this 
problem.  A setter for port does exist on the 
mx4j.tools.naming.NamingService object.

The lastest source for org.apache.jk.common.JkMX does not have this 
feature, and would be the place to incorporate it.


Actually, it does have this feature already.  The option you want is:
  mx.jrmpPort=
This is my first post to the mailing list and have been a long time user 
of Tomcat.

-Kevin

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




This message is intended only for the use of the person(s) listed above as the intended recipient(s), and may contain information that is PRIVILEGED and CONFIDENTIAL.  If you are not an intended recipient, you may not read, copy, or distribute this message or any attachment. If you received this communication in error, please notify us immediately by e-mail and then delete all copies of this message and any attachments.

In addition you should be aware that ordinary (unencrypted) e-mail sent through the Internet is not secure. Do not send confidential or sensitive information, such as social security numbers, account numbers, personal identification numbers and passwords, to us via ordinary (unencrypted) e-mail.





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Kevin Pfarr  Software Engineer
PN:   314.678.2231
FX:   314.436.2559
CELL: 314.629.6255
[EMAIL PROTECTED]
Asynchrony Solutions, Inc.
1709 Washington Avenue // Suite 200
Saint Louis, Missouri 63103
www.asolutions.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


JMX JRMP rmi registry port configuration

2004-01-08 Thread Kevin Pfarr
When JMX is enabled, in the jk2.properties file, and configured to use 
the MX4J JRMP interal adapter, a rmi registry is created and bound to 
the default port of 1099.  If there is another application using that 
port and bind expection is thrown and the adaptor is never enabled.

A configuration option for the rmi registry port would sovle this 
problem.  A setter for port does exist on the 
mx4j.tools.naming.NamingService object.

The lastest source for org.apache.jk.common.JkMX does not have this 
feature, and would be the place to incorporate it.

This is my first post to the mailing list and have been a long time user 
of Tomcat.

-Kevin

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]