All we need to do is put the jmx-remoting jar in /lib/endorsed.
Tim Fox wrote:
Ron Sigal wrote:
> Sorry, I wasn't following this thread. Mostly, I'm going to plead
> ignorance - I've never touched JBoss jmx-remoting. However, Jason
> seems to be on the right track. The line numbers in Tim's stack trace
> don't match the JBoss implementation of
> javax.management.remote.JMXServiceURL.
Other possibilities could be to use an ip address rather than hostname,
or switch to a less restrictive implementation of the classes. I'm not
familiar enough with this area to know what is the best approach, but
the fact of the matter is that JBAS 4.x starts up fine with a hostname
with underscores and JBAS 5 doesn't.
>
> -Ron
>
> Jason T. Greene wrote:
>> OK, I just verified and this is explicitly disallowed in the JDK
>> version of JMXSerivceURL (IMO a bug). It is however allowed in URL.
>>
>> The JBoss implementation of JMXServiceURL does allow it, so the
>> problem is that it is not in endorsed libs.
>>
>> -Jason
>>
>> Jason T. Greene wrote:
>>> No escaping should be needed. The JDK allows underscores in
>>> hostnames. In reality there is nothing wrong with them, they just
>>> aren't allowed in DNS.
>>>
>>> Tim Fox wrote:
>>>>
>>>>
>>>> Dimitris Andreadis wrote:
>>>>> Am I missing the point, or this is JDK code being executed
>>>>> (javax.management...). How escaping the hostname could help?
>>>>
>>>> AFAICT the string is just a JMX service name, it doesn't *have to*
>>>> contain the actual hostname AFAICT:
>>>>
>>>> String serviceURL = "service:jmx:rmi://" + bindAddress +
>>>> "/jndi/rmi://" + bindAddress + ":" + registryPort +
jndiPath;
>>>>
>>>> So should be to escape it before passing it to the JDK code.
>>>>
>>>> Maybe someone from the remoting team should comment, since this is
>>>> remoting code...
>>>>
>>>>>
>>>>> java.net.MalformedURLException: Bad URL path:
>>>>> _laptop/jndi/rmi://tims_laptop:1090/jmxconnector
>>>>> at
>>>>>
javax.management.remote.JMXServiceURL.validate(JMXServiceURL.java:348)
>>>>>
>>>>> at
>>>>>
javax.management.remote.JMXServiceURL.<init>(JMXServiceURL.java:208)
>>>>> at
>>>>>
org.jboss.mx.remoting.service.JMXConnectorServerService.start(JMXConnectorServerService.java:106)
>>>>>
>>>>>
>>>>> This looks like a non-issue to me. Better change your hostname :)
>>>>>
>>>>> Tim Fox wrote:
>>>>>> I'm not familiar with that code, but I'm assuming that
whoever is
>>>>>> generating the URLs should be able to escape any occurences of
>>>>>> '_' pretty easily....
>>>>>>
>>>>>>
>>>>>> Dimitris Andreadis wrote:
>>>>>>> So, is this a JDK problem, or not?
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> jboss-development mailing list
>>>>>>> jboss-development(a)lists.jboss.org
>>>>>>>
https://lists.jboss.org/mailman/listinfo/jboss-development
>>>>>>
>>>>> _______________________________________________
>>>>> jboss-development mailing list
>>>>> jboss-development(a)lists.jboss.org
>>>>>
https://lists.jboss.org/mailman/listinfo/jboss-development
>>>>
>>>
>>>
>>
>>
>
> --
> JBoss, a Division of Red Hat
> "My company's smarter than your company."
> ------------------------------------------------------------------------
>
> _______________________________________________
> jboss-development mailing list
> jboss-development(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jboss-development
>
--
Jason T. Greene
JBoss, a division of Red Hat