Ming,
Is there some multi-homing and/or DNS issue that would cause the port
to be blocked? I notice that the URL is fully qualified by machine
name and domain.
Lloyd
On Aug 15, 2008, at 2:18 PM, Ming Zhang wrote:
> This is what I have in domain.xml:
> <admin-service system-jmx-connector-name="system" type="das-and-
> server">
> <!-- The JSR 160 "system-jmx-connector" -->
> <jmx-connector accept-all="false" address="0.0.0.0" auth-realm-
> name="admin-realm" enabled="true"
> name="system" port="8686" protocol="rmi_jrmp" security-
> enabled="false">
> <ssl cert-nickname="s1as"/>
> </jmx-connector>
>
> This is a new installation of GF V2 (9.1ur1 FCS bits) on this
> machine after the move. Didn't run into any problem like this before
> the move with the same bits. That's why I suspect there is a network
> issue. I was able to start the V3 without problem on this machine.
>
> Thanks,
> Ming
>
> Lloyd Chambers wrote:
>> The first thing to check is the <jmx-connector> entry in
>> domain.xml. Does it specify an old machine name? Look at the
>> client-hostname property in particular.
>>
>> <admin-service system-jmx-connector-name="system" type="das-and-
>> server">
>> <!-- The JSR 160 "system-jmx-connector" -->
>> <jmx-connector accept-all="false" address="0.0.0.0" auth-
>> realm-name="admin-realm" enabled="true" name="system" port="8686"
>> protocol="rmi_jrmp" security-enabled="false">
>> <ssl cert-nickname="s1as" client-auth-enabled="false" ssl2-
>> enabled="false" ssl3-enabled="true" tls-enabled="true" tls-rollback-
>> enabled="true"/>
>> <property name="client-hostname" value="MB2.local"/>
>> </jmx-connector>
>> </admin-service>
>>
>>
>> On Aug 15, 2008, at 12:36 PM, Ming Zhang wrote:
>>
>>> Hi,
>>>
>>> After my solaris 10 machine moved to a new lab, I failed to start
>>> the domain and got following error:
>>>
>>> [#|2008-08-15T10:49:28.664-0700|SEVERE|sun-appserver9.1|
>>> javax.enterprise.system.core|
>>> _ThreadID
>>> =
>>> 10
>>> ;_ThreadName
>>> =
>>> main
>>> ;com
>>> .sun
>>> .enterprise
>>> .admin
>>> .server
>>> .core
>>> .JmxConnectorLifecycle
>>> @5ebac9;com.sun.appserv.server.ServerLifecycleException: Cannot
>>> bind to URL [rmi://jws-280r-1.red.iplanet.com:8686/management/rmi-
>>> jmx-connector]: javax.naming.ServiceUnavailableException [Root
>>> exception is java.rmi.ConnectException: Connection refused to
>>> host: jws-280r-1.red.iplanet.com; nested exception is:
>>> java.net.ConnectException: Connection timed
>>> out];_RequestID=a7c777d5-d597-43d9-a0a8-bd115acf21d5;|Service
>>> com.sun.enterprise.admin.server.core.JmxConnectorLifecycle_at_5ebac9
>>> cannot be started! :
>>> com.sun.appserv.server.ServerLifecycleException: Cannot bind to
>>> URL [rmi://jws-280r-1.red.iplanet.com:8686/management/rmi-jmx-
>>> connector]: javax.naming.ServiceUnavailableException [Root
>>> exception is java.rmi.ConnectException: Connection refused to
>>> host: jws-280r-1.red.iplanet.com; nested exception is:
>>> java.net.ConnectException: Connection timed out]|#]
>>>
>>> Full stack trace:
>>> http://javaweb.sfbay/~mzh777/v2/as91ur1/mysql/startDomain/server.log
>>>
>>> I tried to do a new installation and it hangs for about 5 minutes
>>> at the port availability checking (before the port assignment
>>> screen). Does anyone saw this kind of errors? Is there a simple to
>>> diagnose this network issue?
>>>
>>> Thanks,
>>> Ming
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>