I'm seeing the following message in the server.log file relating to JMX:
[#|2010-06-23T09:39:17.707-0700|WARNING|glassfish3.1|javax.enterprise.system.tools.admin.org.glassfish.server|_ThreadID=73;_ThreadName=Thread-1;|Cannot
start JMX connector: JmxConnector config: { name = system, Protocol =
rmi_jrmp, Address = 0.0.0.0, Port = 28686, AcceptAll = false,
AuthRealmName = admin-realm, SecurityEnabled = true}:
java.lang.IllegalArgumentException: JMXConnectorServer not yet
supporting security|#]
The "default-config" in the domain.xml which is used to initialize the
<config> for a cluster omits the security-enabled="false" attribute from
the <jmx-connector> element in the <admin-service> element. This means
that by default, all instances in clusters will try to create a
security-enabled port for JMX which fails.
To enable JMX for instances, either edit the default-config for the
config for the cluster to set security-enabled=false.
I created issue 12403 for this.
https://glassfish.dev.java.net/issues/show_bug.cgi?id=12403
Tom
On 6/28/2010 4:12 AM, Prasad Subramanian wrote:
> I downloaded the promoted build of 6/23 and unzipped it.
>
> I created a cluster c1 and two instances ins1 and ins2. I then started
> the cluster using asadmin start-cluster c1 as the command.
>
> However , I do not see the JMX listener ports of these two instances
> up and running. Doing a netstat -a does not show these ports to be up
> and listening. The instance processes are up and running.
>
> Is there something that I am missing ?
>
> Thanks
> Prasad
>
>