The error does not impact overall server functionality, it can be
ignored for now.
Details: it means that the JMX RMI connector is unable to start. No
JMX clients will be able to connect (JConsole, etc).
The problem is that TransientContext is refusing to bind a legitimate
JNDI name. Mahesh Kannan has said he'll look into it.
Lloyd
On Jul 29, 2008, at 10:14 AM, Sahoo wrote:
> I have filed https://glassfish.dev.java.net/issues/show_bug.cgi?id=5389
> .
>
> The server continues to function despite that exception.
>
> Thanks,,
> Sahoo
>
> Tim Quinn wrote:
>> I can't recall if others have reported this problem. (I searched
>> the dev alias archives and didn't see anything.)
>>
>> I did a mvn clean; svn update; mvn -U install and get this error
>> during start-up:
>>
>>
>> SEVERE: ERROR starting JMX connector: JmxConnector config: { name =
>> system, Protocol = rmi_jrmp, Address = 0.0.0.0, Port = 8686,
>> AcceptAll = false, AuthRealmName = admin-realm, SecurityEnabled =
>> false}: java.io.IOException: Cannot bind to URL [rmi://
>> 192.168.2.101:8686/management/rmi-jmx-connector]:
>> javax.naming.InvalidNameException: Cannot create empty subcontext
>> Jul 29, 2008 11:58:22 AM
>>
>> I never see the "start-up complete" message at the end of the
>> server.log either.
>>
>> Has anyone else seen this, or does anyone have any suggestions how
>> to get past this?
>>
>> Thanks.
>>
>> - Tim
>>
>> ---------------------------------------------------------------------
>> 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
>