5:31 a.m.
Just tried to start JB5 on my laptop, and it fails.
Seems like something in remoting doesn't like hostnames with an
underscore in them?
My hostname is "tims_laptop".
AS 4.x starts fine on the same machine.
11:05:17,197 ERROR [AbstractKernelController] Error installing to Start:
name=jboss.remoting:protocol=rmi,service=JMXConnectorServer state=Create
mode=Manual requiredState=Installed
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)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:184)
at $Proxy4.start(Unknown Source)
at
org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:42)
at
org.jboss.system.microcontainer.ServiceControllerContextAction.install(ServiceControllerContextAction.java:46)
at
org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
at
org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327)
at
org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:239)
at
org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309)
at
org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784)
at
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:622)
at
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411)
at
org.jboss.system.ServiceController.doChange(ServiceController.java:659)
at
org.jboss.system.ServiceController.start(ServiceController.java:431)
at
org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:149)
at
org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:107)
at
org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:46)
at
org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.deploy(AbstractSimpleRealDeployer.java:65)
at
org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:728)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:749)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:669)
at
org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327)
at
org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309)
at
org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784)
at
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:622)
at
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:495)
at
org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:354)
at
org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:245)
at
org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:131)
at
org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:382)
at org.jboss.Main.boot(Main.java:210)
at org.jboss.Main$1.run(Main.java:529)
at java.lang.Thread.run(Thread.java:595)
11:05:17,203 ERROR [AbstractKernelController] Error installing to Real:
name=vfsfile:/home/tim/dev/jbas/trunk/build/output/jboss-5.0.0.Beta3/server/default/deploy/jmx-remoting.sar/
state=PostClassLoader mode=Manual requiredState=Real
org.jboss.deployers.spi.DeploymentException: Error deploying:
jboss.remoting:service=JMXConnectorServer,protocol=rmi
at
org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
at
org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:126)
at
org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:46)
at
org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.deploy(AbstractSimpleRealDeployer.java:65)
at
org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:728)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:749)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:669)
at
org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327)
at
org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309)
at
org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784)
at
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:622)
at
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:495)
at
org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:354)
at
org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:245)
at
org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:131)
at
org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:382)
at org.jboss.Main.boot(Main.java:210)
at org.jboss.Main$1.run(Main.java:529)
at java.lang.Thread.run(Thread.java:595)
--
Tim Fox
Messaging lead
JBoss - a division of Red Hat
5:41 a.m.
http://en.wikipedia.org/wiki/Hostname :
"Underscore characters are commonly used by Windows systems but
according to RFC 952 they are not allowed and several systems, such as
DomainKeys and the SRV record deliberately use the underscore to make
sure their special domain names are not confused with a hostname."
So we can add AS 5 to the list.
Carlo
On Wed, 2007-10-10 at 11:31 +0100, Tim Fox wrote:
Just tried to start JB5 on my laptop, and it fails.
Seems like something in remoting doesn't like hostnames with an
underscore in them?
My hostname is "tims_laptop".
AS 4.x starts fine on the same machine.
11:05:17,197 ERROR [AbstractKernelController] Error installing to Start:
name=jboss.remoting:protocol=rmi,service=JMXConnectorServer state=Create
mode=Manual requiredState=Installed
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)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:184)
at $Proxy4.start(Unknown Source)
at
org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:42)
at
org.jboss.system.microcontainer.ServiceControllerContextAction.install(ServiceControllerContextAction.java:46)
at
org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
at
org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327)
at
org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:239)
at
org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309)
at
org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784)
at
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:622)
at
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411)
at
org.jboss.system.ServiceController.doChange(ServiceController.java:659)
at
org.jboss.system.ServiceController.start(ServiceController.java:431)
at
org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:149)
at
org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:107)
at
org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:46)
at
org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.deploy(AbstractSimpleRealDeployer.java:65)
at
org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:728)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:749)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:669)
at
org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327)
at
org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309)
at
org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784)
at
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:622)
at
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:495)
at
org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:354)
at
org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:245)
at
org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:131)
at
org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:382)
at org.jboss.Main.boot(Main.java:210)
at org.jboss.Main$1.run(Main.java:529)
at java.lang.Thread.run(Thread.java:595)
11:05:17,203 ERROR [AbstractKernelController] Error installing to Real:
name=vfsfile:/home/tim/dev/jbas/trunk/build/output/jboss-5.0.0.Beta3/server/default/deploy/jmx-remoting.sar/
state=PostClassLoader mode=Manual requiredState=Real
org.jboss.deployers.spi.DeploymentException: Error deploying:
jboss.remoting:service=JMXConnectorServer,protocol=rmi
at
org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
at
org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:126)
at
org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:46)
at
org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.deploy(AbstractSimpleRealDeployer.java:65)
at
org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:728)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:749)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:669)
at
org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327)
at
org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309)
at
org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862)
at
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784)
at
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:622)
at
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411)
at
org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:495)
at
org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:354)
at
org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:245)
at
org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:131)
at
org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:382)
at org.jboss.Main.boot(Main.java:210)
at org.jboss.Main$1.run(Main.java:529)
at java.lang.Thread.run(Thread.java:595)
5:46 a.m.
Carlo de Wolf wrote:
http://en.wikipedia.org/wiki/Hostname :
"Underscore characters are commonly used by Windows systems but
according to RFC 952 they are not allowed and several systems, such as
DomainKeys and the SRV record deliberately use the underscore to make
sure their special domain names are not confused with a hostname."
BTW I'm running Linux (FC6).
Although if we go by the letter of the law we could disallow such
hostnames, I think the question here is whether we want to p off all
those JBAS 4.x users with underscores in their hostnames who try to
upgrade to JB5, hit this, and hate JBoss for ever... :)
So we can add AS 5 to the list.
Carlo
On Wed, 2007-10-10 at 11:31 +0100, Tim Fox wrote:
> Just tried to start JB5 on my laptop, and it fails.
>
> Seems like something in remoting doesn't like hostnames with an
> underscore in them?
>
> My hostname is "tims_laptop".
>
> AS 4.x starts fine on the same machine.
>
> 11:05:17,197 ERROR [AbstractKernelController] Error installing to Start:
> name=jboss.remoting:protocol=rmi,service=JMXConnectorServer state=Create
> mode=Manual requiredState=Installed
> 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)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
>
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
> at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
> at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> at
> org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> at
> org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
> at
> org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:184)
> at $Proxy4.start(Unknown Source)
> at
>
org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:42)
> at
>
org.jboss.system.microcontainer.ServiceControllerContextAction.install(ServiceControllerContextAction.java:46)
> at
>
org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
> at
>
org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327)
> at
>
org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:239)
> at
>
org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309)
> at
>
org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734)
> at
>
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862)
> at
>
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784)
> at
> org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:622)
> at
> org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411)
> at
> org.jboss.system.ServiceController.doChange(ServiceController.java:659)
> at
> org.jboss.system.ServiceController.start(ServiceController.java:431)
> at
> org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:149)
> at
> org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:107)
> at
> org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:46)
> at
>
org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.deploy(AbstractSimpleRealDeployer.java:65)
> at
>
org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169)
> at
>
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:728)
> at
>
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:749)
> at
> org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:669)
> at
>
org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327)
> at
>
org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309)
> at
>
org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734)
> at
>
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862)
> at
>
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784)
> at
> org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:622)
> at
> org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411)
> at
> org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:495)
> at
> org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:354)
> at
>
org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:245)
> at
>
org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:131)
> at
> org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:382)
> at org.jboss.Main.boot(Main.java:210)
> at org.jboss.Main$1.run(Main.java:529)
> at java.lang.Thread.run(Thread.java:595)
> 11:05:17,203 ERROR [AbstractKernelController] Error installing to Real:
>
name=vfsfile:/home/tim/dev/jbas/trunk/build/output/jboss-5.0.0.Beta3/server/default/deploy/jmx-remoting.sar/
> state=PostClassLoader mode=Manual requiredState=Real
> org.jboss.deployers.spi.DeploymentException: Error deploying:
> jboss.remoting:service=JMXConnectorServer,protocol=rmi
> at
>
org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
> at
> org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:126)
> at
> org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:46)
> at
>
org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.deploy(AbstractSimpleRealDeployer.java:65)
> at
>
org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169)
> at
>
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:728)
> at
>
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:749)
> at
> org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:669)
> at
>
org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327)
> at
>
org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309)
> at
>
org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734)
> at
>
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862)
> at
>
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784)
> at
> org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:622)
> at
> org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411)
> at
> org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:495)
> at
> org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:354)
> at
>
org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:245)
> at
>
org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:131)
> at
> org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:382)
> at org.jboss.Main.boot(Main.java:210)
> at org.jboss.Main$1.run(Main.java:529)
> at java.lang.Thread.run(Thread.java:595)
>
>
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
--
Tim Fox
Messaging lead
JBoss - a division of Red Hat
6:29 a.m.
I agree with Tim here, is that in our code or in the the JDK's code?
On 10/10/2007 12:46 PM, Tim Fox wrote:
Carlo de Wolf wrote:
> http://en.wikipedia.org/wiki/Hostname :
> "Underscore characters are commonly used by Windows systems but
> according to RFC 952 they are not allowed and several systems, such as
> DomainKeys and the SRV record deliberately use the underscore to make
> sure their special domain names are not confused with a hostname."
BTW I'm running Linux (FC6).
Although if we go by the letter of the law we could disallow such
hostnames, I think the question here is whether we want to p off all
those JBAS 4.x users with underscores in their hostnames who try to
upgrade to JB5, hit this, and hate JBoss for ever... :)
>
> So we can add AS 5 to the list.
>
> Carlo
>
> On Wed, 2007-10-10 at 11:31 +0100, Tim Fox wrote:
>> Just tried to start JB5 on my laptop, and it fails.
>>
>> Seems like something in remoting doesn't like hostnames with an
>> underscore in them?
>>
>> My hostname is "tims_laptop".
>>
>> AS 4.x starts fine on the same machine.
>>
>> 11:05:17,197 ERROR [AbstractKernelController] Error installing to
>> Start: name=jboss.remoting:protocol=rmi,service=JMXConnectorServer
>> state=Create mode=Manual requiredState=Installed
>> 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)
>>
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>
>> at
>>
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>
>> at java.lang.reflect.Method.invoke(Method.java:585)
>> at
>> org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
>>
>> at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
>> at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
>> at
>> org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
>>
>> at
>> org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
>> at
>> org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:184)
>>
>> at $Proxy4.start(Unknown Source)
>> at
>>
org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:42)
>>
>> at
>>
org.jboss.system.microcontainer.ServiceControllerContextAction.install(ServiceControllerContextAction.java:46)
>>
>> at
>>
org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
>>
>> at
>>
org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327)
>>
>> at
>>
org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:239)
>>
>> at
>>
org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309)
>>
>> at
>>
org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734)
>>
>> at
>>
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862)
>>
>> at
>>
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784)
>>
>> at
>>
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:622)
>>
>> at
>>
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411)
>>
>> at
>> org.jboss.system.ServiceController.doChange(ServiceController.java:659)
>> at
>> org.jboss.system.ServiceController.start(ServiceController.java:431)
>> at
>> org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:149)
>>
>> at
>> org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:107)
>>
>> at
>> org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:46)
>>
>> at
>>
org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.deploy(AbstractSimpleRealDeployer.java:65)
>>
>> at
>>
org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169)
>>
>> at
>>
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:728)
>>
>> at
>>
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:749)
>>
>> at
>>
org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:669)
>>
>> at
>>
org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327)
>>
>> at
>>
org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309)
>>
>> at
>>
org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734)
>>
>> at
>>
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862)
>>
>> at
>>
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784)
>>
>> at
>>
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:622)
>>
>> at
>>
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411)
>>
>> at
>>
org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:495)
>>
>> at
>>
org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:354)
>>
>> at
>>
org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:245)
>>
>> at
>>
org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:131)
>>
>> at
>> org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:382)
>>
>> at org.jboss.Main.boot(Main.java:210)
>> at org.jboss.Main$1.run(Main.java:529)
>> at java.lang.Thread.run(Thread.java:595)
>> 11:05:17,203 ERROR [AbstractKernelController] Error installing to
>> Real:
>>
name=vfsfile:/home/tim/dev/jbas/trunk/build/output/jboss-5.0.0.Beta3/server/default/deploy/jmx-remoting.sar/
>> state=PostClassLoader mode=Manual requiredState=Real
>> org.jboss.deployers.spi.DeploymentException: Error deploying:
>> jboss.remoting:service=JMXConnectorServer,protocol=rmi
>> at
>>
org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
>>
>> at
>> org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:126)
>>
>> at
>> org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:46)
>>
>> at
>>
org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.deploy(AbstractSimpleRealDeployer.java:65)
>>
>> at
>>
org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169)
>>
>> at
>>
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:728)
>>
>> at
>>
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:749)
>>
>> at
>>
org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:669)
>>
>> at
>>
org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327)
>>
>> at
>>
org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309)
>>
>> at
>>
org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734)
>>
>> at
>>
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862)
>>
>> at
>>
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784)
>>
>> at
>>
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:622)
>>
>> at
>>
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411)
>>
>> at
>>
org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:495)
>>
>> at
>>
org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:354)
>>
>> at
>>
org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:245)
>>
>> at
>>
org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:131)
>>
>> at
>> org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:382)
>>
>> at org.jboss.Main.boot(Main.java:210)
>> at org.jboss.Main$1.run(Main.java:529)
>> at java.lang.Thread.run(Thread.java:595)
>>
>>
>
> _______________________________________________
> jboss-development mailing list
> jboss-development(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development
7:01 a.m.
In principal I don't agree. Just because some sly Fox is using an OS
that doesn't stick to rules we shouldn't modify our code.
root@ubuntu:~# hostname ubuntu_test
hostname: the specified hostname is invalid
But it would appear that I'm being overtrumped.
Carlo
PS. This would make a great thread on memo-list.
On Wed, 2007-10-10 at 13:29 +0200, Sacha Labourey wrote:
I agree with Tim here, is that in our code or in the the JDK's
code?
On 10/10/2007 12:46 PM, Tim Fox wrote:
>
>
> Carlo de Wolf wrote:
>> http://en.wikipedia.org/wiki/Hostname :
>> "Underscore characters are commonly used by Windows systems but
>> according to RFC 952 they are not allowed and several systems, such as
>> DomainKeys and the SRV record deliberately use the underscore to make
>> sure their special domain names are not confused with a hostname."
>
> BTW I'm running Linux (FC6).
>
> Although if we go by the letter of the law we could disallow such
> hostnames, I think the question here is whether we want to p off all
> those JBAS 4.x users with underscores in their hostnames who try to
> upgrade to JB5, hit this, and hate JBoss for ever... :)
>>
>> So we can add AS 5 to the list.
>>
>> Carlo
>>
>> On Wed, 2007-10-10 at 11:31 +0100, Tim Fox wrote:
>>> Just tried to start JB5 on my laptop, and it fails.
>>>
>>> Seems like something in remoting doesn't like hostnames with an
>>> underscore in them?
>>>
>>> My hostname is "tims_laptop".
>>>
>>> AS 4.x starts fine on the same machine.
>>>
>>> 11:05:17,197 ERROR [AbstractKernelController] Error installing to
>>> Start: name=jboss.remoting:protocol=rmi,service=JMXConnectorServer
>>> state=Create mode=Manual requiredState=Installed
>>> 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)
>>>
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>>
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>
>>> at
>>>
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>
>>> at java.lang.reflect.Method.invoke(Method.java:585)
>>> at
>>>
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
>>>
>>> at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
>>> at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
>>> at
>>>
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
>>>
>>> at
>>> org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
>>> at
>>> org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:184)
>>>
>>> at $Proxy4.start(Unknown Source)
>>> at
>>>
org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:42)
>>>
>>> at
>>>
org.jboss.system.microcontainer.ServiceControllerContextAction.install(ServiceControllerContextAction.java:46)
>>>
>>> at
>>>
org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
>>>
>>> at
>>>
org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327)
>>>
>>> at
>>>
org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:239)
>>>
>>> at
>>>
org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309)
>>>
>>> at
>>>
org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734)
>>>
>>> at
>>>
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862)
>>>
>>> at
>>>
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784)
>>>
>>> at
>>>
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:622)
>>>
>>> at
>>>
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411)
>>>
>>> at
>>> org.jboss.system.ServiceController.doChange(ServiceController.java:659)
>>> at
>>> org.jboss.system.ServiceController.start(ServiceController.java:431)
>>> at
>>> org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:149)
>>>
>>> at
>>> org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:107)
>>>
>>> at
>>> org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:46)
>>>
>>> at
>>>
org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.deploy(AbstractSimpleRealDeployer.java:65)
>>>
>>> at
>>>
org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169)
>>>
>>> at
>>>
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:728)
>>>
>>> at
>>>
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:749)
>>>
>>> at
>>>
org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:669)
>>>
>>> at
>>>
org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327)
>>>
>>> at
>>>
org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309)
>>>
>>> at
>>>
org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734)
>>>
>>> at
>>>
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862)
>>>
>>> at
>>>
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784)
>>>
>>> at
>>>
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:622)
>>>
>>> at
>>>
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411)
>>>
>>> at
>>>
org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:495)
>>>
>>> at
>>>
org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:354)
>>>
>>> at
>>>
org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:245)
>>>
>>> at
>>>
org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:131)
>>>
>>> at
>>> org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:382)
>>>
>>> at org.jboss.Main.boot(Main.java:210)
>>> at org.jboss.Main$1.run(Main.java:529)
>>> at java.lang.Thread.run(Thread.java:595)
>>> 11:05:17,203 ERROR [AbstractKernelController] Error installing to
>>> Real:
>>>
name=vfsfile:/home/tim/dev/jbas/trunk/build/output/jboss-5.0.0.Beta3/server/default/deploy/jmx-remoting.sar/
>>> state=PostClassLoader mode=Manual requiredState=Real
>>> org.jboss.deployers.spi.DeploymentException: Error deploying:
>>> jboss.remoting:service=JMXConnectorServer,protocol=rmi
>>> at
>>>
org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
>>>
>>> at
>>> org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:126)
>>>
>>> at
>>> org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:46)
>>>
>>> at
>>>
org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.deploy(AbstractSimpleRealDeployer.java:65)
>>>
>>> at
>>>
org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169)
>>>
>>> at
>>>
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:728)
>>>
>>> at
>>>
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:749)
>>>
>>> at
>>>
org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:669)
>>>
>>> at
>>>
org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327)
>>>
>>> at
>>>
org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309)
>>>
>>> at
>>>
org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734)
>>>
>>> at
>>>
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862)
>>>
>>> at
>>>
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784)
>>>
>>> at
>>>
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:622)
>>>
>>> at
>>>
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411)
>>>
>>> at
>>>
org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:495)
>>>
>>> at
>>>
org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:354)
>>>
>>> at
>>>
org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:245)
>>>
>>> at
>>>
org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:131)
>>>
>>> at
>>> org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:382)
>>>
>>> at org.jboss.Main.boot(Main.java:210)
>>> at org.jboss.Main$1.run(Main.java:529)
>>> at java.lang.Thread.run(Thread.java:595)
>>>
>>>
>>
>> _______________________________________________
>> 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
7:08 a.m.
well, as you know when it comes to spec (like TCP/IP):
- implement it so that you restrict yourself to the max, but
- accept more than the spec restrict you to
Now, pragmatically: will some significant number of people using jboss
have a "-" in their hostname? yes :) we are done.
On 10/10/2007 02:01 PM, Carlo de Wolf wrote:
In principal I don't agree. Just because some sly Fox is using an
OS
that doesn't stick to rules we shouldn't modify our code.
root@ubuntu:~# hostname ubuntu_test
hostname: the specified hostname is invalid
But it would appear that I'm being overtrumped.
Carlo
PS. This would make a great thread on memo-list.
On Wed, 2007-10-10 at 13:29 +0200, Sacha Labourey wrote:
> I agree with Tim here, is that in our code or in the the JDK's code?
>
> On 10/10/2007 12:46 PM, Tim Fox wrote:
>>
>> Carlo de Wolf wrote:
>>> http://en.wikipedia.org/wiki/Hostname :
>>> "Underscore characters are commonly used by Windows systems but
>>> according to RFC 952 they are not allowed and several systems, such as
>>> DomainKeys and the SRV record deliberately use the underscore to make
>>> sure their special domain names are not confused with a hostname."
>> BTW I'm running Linux (FC6).
>>
>> Although if we go by the letter of the law we could disallow such
>> hostnames, I think the question here is whether we want to p off all
>> those JBAS 4.x users with underscores in their hostnames who try to
>> upgrade to JB5, hit this, and hate JBoss for ever... :)
>>> So we can add AS 5 to the list.
>>>
>>> Carlo
>>>
>>> On Wed, 2007-10-10 at 11:31 +0100, Tim Fox wrote:
>>>> Just tried to start JB5 on my laptop, and it fails.
>>>>
>>>> Seems like something in remoting doesn't like hostnames with an
>>>> underscore in them?
>>>>
>>>> My hostname is "tims_laptop".
>>>>
>>>> AS 4.x starts fine on the same machine.
>>>>
>>>> 11:05:17,197 ERROR [AbstractKernelController] Error installing to
>>>> Start: name=jboss.remoting:protocol=rmi,service=JMXConnectorServer
>>>> state=Create mode=Manual requiredState=Installed
>>>> 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)
>>>>
>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>> at
>>>>
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>>
>>>> at
>>>>
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>
>>>> at java.lang.reflect.Method.invoke(Method.java:585)
>>>> at
>>>>
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
>>>>
>>>> at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
>>>> at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
>>>> at
>>>>
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
>>>>
>>>> at
>>>> org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
>>>> at
>>>>
org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:184)
>>>>
>>>> at $Proxy4.start(Unknown Source)
>>>> at
>>>>
org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:42)
>>>>
>>>> at
>>>>
org.jboss.system.microcontainer.ServiceControllerContextAction.install(ServiceControllerContextAction.java:46)
>>>>
>>>> at
>>>>
org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
>>>>
>>>> at
>>>>
org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327)
>>>>
>>>> at
>>>>
org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:239)
>>>>
>>>> at
>>>>
org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309)
>>>>
>>>> at
>>>>
org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734)
>>>>
>>>> at
>>>>
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862)
>>>>
>>>> at
>>>>
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784)
>>>>
>>>> at
>>>>
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:622)
>>>>
>>>> at
>>>>
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411)
>>>>
>>>> at
>>>> org.jboss.system.ServiceController.doChange(ServiceController.java:659)
>>>> at
>>>> org.jboss.system.ServiceController.start(ServiceController.java:431)
>>>> at
>>>>
org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:149)
>>>>
>>>> at
>>>>
org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:107)
>>>>
>>>> at
>>>>
org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:46)
>>>>
>>>> at
>>>>
org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.deploy(AbstractSimpleRealDeployer.java:65)
>>>>
>>>> at
>>>>
org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169)
>>>>
>>>> at
>>>>
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:728)
>>>>
>>>> at
>>>>
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:749)
>>>>
>>>> at
>>>>
org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:669)
>>>>
>>>> at
>>>>
org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327)
>>>>
>>>> at
>>>>
org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309)
>>>>
>>>> at
>>>>
org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734)
>>>>
>>>> at
>>>>
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862)
>>>>
>>>> at
>>>>
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784)
>>>>
>>>> at
>>>>
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:622)
>>>>
>>>> at
>>>>
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411)
>>>>
>>>> at
>>>>
org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:495)
>>>>
>>>> at
>>>>
org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:354)
>>>>
>>>> at
>>>>
org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:245)
>>>>
>>>> at
>>>>
org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:131)
>>>>
>>>> at
>>>> org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:382)
>>>>
>>>> at org.jboss.Main.boot(Main.java:210)
>>>> at org.jboss.Main$1.run(Main.java:529)
>>>> at java.lang.Thread.run(Thread.java:595)
>>>> 11:05:17,203 ERROR [AbstractKernelController] Error installing to
>>>> Real:
>>>>
name=vfsfile:/home/tim/dev/jbas/trunk/build/output/jboss-5.0.0.Beta3/server/default/deploy/jmx-remoting.sar/
>>>> state=PostClassLoader mode=Manual requiredState=Real
>>>> org.jboss.deployers.spi.DeploymentException: Error deploying:
>>>> jboss.remoting:service=JMXConnectorServer,protocol=rmi
>>>> at
>>>>
org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
>>>>
>>>> at
>>>>
org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:126)
>>>>
>>>> at
>>>>
org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:46)
>>>>
>>>> at
>>>>
org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.deploy(AbstractSimpleRealDeployer.java:65)
>>>>
>>>> at
>>>>
org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169)
>>>>
>>>> at
>>>>
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:728)
>>>>
>>>> at
>>>>
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:749)
>>>>
>>>> at
>>>>
org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:669)
>>>>
>>>> at
>>>>
org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327)
>>>>
>>>> at
>>>>
org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309)
>>>>
>>>> at
>>>>
org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734)
>>>>
>>>> at
>>>>
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862)
>>>>
>>>> at
>>>>
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784)
>>>>
>>>> at
>>>>
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:622)
>>>>
>>>> at
>>>>
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411)
>>>>
>>>> at
>>>>
org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:495)
>>>>
>>>> at
>>>>
org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:354)
>>>>
>>>> at
>>>>
org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:245)
>>>>
>>>> at
>>>>
org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:131)
>>>>
>>>> at
>>>> org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:382)
>>>>
>>>> at org.jboss.Main.boot(Main.java:210)
>>>> at org.jboss.Main$1.run(Main.java:529)
>>>> at java.lang.Thread.run(Thread.java:595)
>>>>
>>>>
>>> _______________________________________________
>>> 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-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
7:12 a.m.
Sacha Labourey wrote, On 10/10/2007 03:08 PM (EEST):
well, as you know when it comes to spec (like TCP/IP):
- implement it so that you restrict yourself to the max, but
- accept more than the spec restrict you to
Now, pragmatically: will some significant number of people using jboss
have a "-" in their hostname? yes :) we are done.
only underscore matters "_", "-" is ok.
On 10/10/2007 02:01 PM, Carlo de Wolf wrote:
> In principal I don't agree. Just because some sly Fox is using an OS
> that doesn't stick to rules we shouldn't modify our code.
>
> root@ubuntu:~# hostname ubuntu_test
> hostname: the specified hostname is invalid
>
> But it would appear that I'm being overtrumped.
>
> Carlo
>
> PS. This would make a great thread on memo-list.
>
> On Wed, 2007-10-10 at 13:29 +0200, Sacha Labourey wrote:
>> I agree with Tim here, is that in our code or in the the JDK's code?
>>
>> On 10/10/2007 12:46 PM, Tim Fox wrote:
>>>
>>> Carlo de Wolf wrote:
>>>> http://en.wikipedia.org/wiki/Hostname :
>>>> "Underscore characters are commonly used by Windows systems but
>>>> according to RFC 952 they are not allowed and several systems, such as
>>>> DomainKeys and the SRV record deliberately use the underscore to make
>>>> sure their special domain names are not confused with a hostname."
>>> BTW I'm running Linux (FC6).
>>>
>>> Although if we go by the letter of the law we could disallow such
>>> hostnames, I think the question here is whether we want to p off all
>>> those JBAS 4.x users with underscores in their hostnames who try to
>>> upgrade to JB5, hit this, and hate JBoss for ever... :)
>>>> So we can add AS 5 to the list.
>>>>
>>>> Carlo
>>>>
>>>> On Wed, 2007-10-10 at 11:31 +0100, Tim Fox wrote:
>>>>> Just tried to start JB5 on my laptop, and it fails.
>>>>>
>>>>> Seems like something in remoting doesn't like hostnames with an
>>>>> underscore in them?
>>>>>
>>>>> My hostname is "tims_laptop".
>>>>>
>>>>> AS 4.x starts fine on the same machine.
>>>>>
>>>>> 11:05:17,197 ERROR [AbstractKernelController] Error installing to
>>>>> Start: name=jboss.remoting:protocol=rmi,service=JMXConnectorServer
>>>>> state=Create mode=Manual requiredState=Installed
>>>>> 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)
>>>>>
>>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>>>> Method)
>>>>> at
>>>>>
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>>>
>>>>> at
>>>>>
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>>
>>>>> at java.lang.reflect.Method.invoke(Method.java:585)
>>>>> at
>>>>>
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
>>>>>
>>>>> at
>>>>> org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
>>>>> at
org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
>>>>> at
>>>>>
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
>>>>>
>>>>> at
>>>>> org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
>>>>> at
>>>>>
org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:184)
>>>>>
>>>>> at $Proxy4.start(Unknown Source)
>>>>> at
>>>>>
org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:42)
>>>>>
>>>>> at
>>>>>
org.jboss.system.microcontainer.ServiceControllerContextAction.install(ServiceControllerContextAction.java:46)
>>>>>
>>>>> at
>>>>>
org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
>>>>>
>>>>> at
>>>>>
org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327)
>>>>>
>>>>> at
>>>>>
org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:239)
>>>>>
>>>>> at
>>>>>
org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309)
>>>>>
>>>>> at
>>>>>
org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734)
>>>>>
>>>>> at
>>>>>
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862)
>>>>>
>>>>> at
>>>>>
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784)
>>>>>
>>>>> at
>>>>>
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:622)
>>>>>
>>>>> at
>>>>>
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411)
>>>>>
>>>>> at
>>>>>
org.jboss.system.ServiceController.doChange(ServiceController.java:659)
>>>>>
>>>>> at
>>>>> org.jboss.system.ServiceController.start(ServiceController.java:431)
>>>>> at
>>>>>
org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:149)
>>>>>
>>>>> at
>>>>>
org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:107)
>>>>>
>>>>> at
>>>>>
org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:46)
>>>>>
>>>>> at
>>>>>
org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.deploy(AbstractSimpleRealDeployer.java:65)
>>>>>
>>>>> at
>>>>>
org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169)
>>>>>
>>>>> at
>>>>>
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:728)
>>>>>
>>>>> at
>>>>>
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:749)
>>>>>
>>>>> at
>>>>>
org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:669)
>>>>>
>>>>> at
>>>>>
org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327)
>>>>>
>>>>> at
>>>>>
org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309)
>>>>>
>>>>> at
>>>>>
org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734)
>>>>>
>>>>> at
>>>>>
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862)
>>>>>
>>>>> at
>>>>>
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784)
>>>>>
>>>>> at
>>>>>
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:622)
>>>>>
>>>>> at
>>>>>
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411)
>>>>>
>>>>> at
>>>>>
org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:495)
>>>>>
>>>>> at
>>>>>
org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:354)
>>>>>
>>>>> at
>>>>>
org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:245)
>>>>>
>>>>> at
>>>>>
org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:131)
>>>>>
>>>>> at
>>>>>
org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:382)
>>>>>
>>>>> at org.jboss.Main.boot(Main.java:210)
>>>>> at org.jboss.Main$1.run(Main.java:529)
>>>>> at java.lang.Thread.run(Thread.java:595)
>>>>> 11:05:17,203 ERROR [AbstractKernelController] Error installing to
>>>>> Real:
>>>>>
name=vfsfile:/home/tim/dev/jbas/trunk/build/output/jboss-5.0.0.Beta3/server/default/deploy/jmx-remoting.sar/
>>>>> state=PostClassLoader mode=Manual requiredState=Real
>>>>> org.jboss.deployers.spi.DeploymentException: Error deploying:
>>>>> jboss.remoting:service=JMXConnectorServer,protocol=rmi
>>>>> at
>>>>>
org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
>>>>>
>>>>> at
>>>>>
org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:126)
>>>>>
>>>>> at
>>>>>
org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:46)
>>>>>
>>>>> at
>>>>>
org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.deploy(AbstractSimpleRealDeployer.java:65)
>>>>>
>>>>> at
>>>>>
org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169)
>>>>>
>>>>> at
>>>>>
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:728)
>>>>>
>>>>> at
>>>>>
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:749)
>>>>>
>>>>> at
>>>>>
org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:669)
>>>>>
>>>>> at
>>>>>
org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327)
>>>>>
>>>>> at
>>>>>
org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309)
>>>>>
>>>>> at
>>>>>
org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734)
>>>>>
>>>>> at
>>>>>
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862)
>>>>>
>>>>> at
>>>>>
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784)
>>>>>
>>>>> at
>>>>>
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:622)
>>>>>
>>>>> at
>>>>>
org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411)
>>>>>
>>>>> at
>>>>>
org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:495)
>>>>>
>>>>> at
>>>>>
org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:354)
>>>>>
>>>>> at
>>>>>
org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:245)
>>>>>
>>>>> at
>>>>>
org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:131)
>>>>>
>>>>> at
>>>>>
org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:382)
>>>>>
>>>>> at org.jboss.Main.boot(Main.java:210)
>>>>> at org.jboss.Main$1.run(Main.java:529)
>>>>> at java.lang.Thread.run(Thread.java:595)
>>>>>
>>>>>
>>>> _______________________________________________
>>>> 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-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
7:17 a.m.
On 10/10/2007 02:12 PM, Aleksandar Kostadinov wrote:
Sacha Labourey wrote, On 10/10/2007 03:08 PM (EEST):
> well, as you know when it comes to spec (like TCP/IP):
> - implement it so that you restrict yourself to the max, but
> - accept more than the spec restrict you to
>
> Now, pragmatically: will some significant number of people using jboss
> have a "-" in their hostname? yes :) we are done.
only underscore matters "_", "-" is ok.
yeah, yeah, you've got my point ;)
7:18 a.m.
Carlo de Wolf wrote:
In principal I don't agree. Just because some sly Fox is using an
OS
that doesn't stick to rules we shouldn't modify our code.
root@ubuntu:~# hostname ubuntu_test
hostname: the specified hostname is invalid
But it would appear that I'm being overtrumped.
Carlo
root@fedora:~# hostname fedora_test
root@fedora_test:~#
;)
No RHEL around, sorry
7:29 a.m.
Thomas Heute wrote:
Carlo de Wolf wrote:
> In principal I don't agree. Just because some sly Fox is using an OS
> that doesn't stick to rules we shouldn't modify our code.
>
> root@ubuntu:~# hostname ubuntu_test
> hostname: the specified hostname is invalid
>
> But it would appear that I'm being overtrumped.
>
> Carlo
root@fedora:~# hostname fedora_test
root@fedora_test:~#
;)
No RHEL around, sorry
FYI:
By chance, i didn't switch back to my previous hostname, starting JBoss
AS 4.2.1.GA failed on me.
Caused by: java.lang.RuntimeException: Exception creating identity:
fedora_test: fedora_test
at org.jboss.remoting.ident.Identity.get(Identity.java:211)
at
org.jboss.remoting.network.NetworkRegistry.preRegister(NetworkRegistry.java:268)
at
org.jboss.mx.server.AbstractMBeanInvoker.invokePreRegister(AbstractMBeanInvoker.java:966)
at
org.jboss.mx.modelmbean.ModelMBeanInvoker.invokePreRegister(ModelMBeanInvoker.java:489)
at
org.jboss.mx.server.AbstractMBeanInvoker.preRegister(AbstractMBeanInvoker.java:654)
at
org.jboss.mx.server.registry.BasicMBeanRegistry.invokePreRegister(BasicMBeanRegistry.java:697)
... 56 more
7:32 a.m.
Thomas Heute wrote:
Thomas Heute wrote:
> Carlo de Wolf wrote:
>> In principal I don't agree. Just because some sly Fox is using an OS
>> that doesn't stick to rules we shouldn't modify our code.
>>
>> root@ubuntu:~# hostname ubuntu_test
>> hostname: the specified hostname is invalid
>>
>> But it would appear that I'm being overtrumped.
>>
>> Carlo
>
>
> root@fedora:~# hostname fedora_test
> root@fedora_test:~#
>
> ;)
>
> No RHEL around, sorry
FYI:
By chance, i didn't switch back to my previous hostname, starting JBoss
AS 4.2.1.GA failed on me.
Caused by: java.lang.RuntimeException: Exception creating identity:
fedora_test: fedora_test
at org.jboss.remoting.ident.Identity.get(Identity.java:211)
at
org.jboss.remoting.network.NetworkRegistry.preRegister(NetworkRegistry.java:268)
at
org.jboss.mx.server.AbstractMBeanInvoker.invokePreRegister(AbstractMBeanInvoker.java:966)
at
org.jboss.mx.modelmbean.ModelMBeanInvoker.invokePreRegister(ModelMBeanInvoker.java:489)
at
org.jboss.mx.server.AbstractMBeanInvoker.preRegister(AbstractMBeanInvoker.java:654)
at
org.jboss.mx.server.registry.BasicMBeanRegistry.invokePreRegister(BasicMBeanRegistry.java:697)
... 56 more
I think that's because hostname doesn't actually update your /etc/hosts
file so anything that tries to resolve the ip address for your new
hostname fails.
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
--
Tim Fox
Messaging lead
JBoss - a division of Red Hat
6:08 a.m.
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
--
Tim Fox
Messaging lead
JBoss - a division of Red Hat
6:31 a.m.
Am I missing the point, or this is JDK code being executed (javax.management...). How
escaping the hostname could help?
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
6:40 a.m.
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
--
Tim Fox
Messaging lead
JBoss - a division of Red Hat
6:46 a.m.
Ok, let's hear from Ron.
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
6:48 a.m.
Also bear in mind that this worked with AS 4.x, so bearing in mind that
Java is Turing-complete, logically there must be some way of working
around this ;)
Dimitris Andreadis wrote:
Ok, let's hear from Ron.
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-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
--
Tim Fox
Messaging lead
JBoss - a division of Red Hat
9:24 a.m.
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
--
Jason T. Greene
JBoss, a division of Red Hat
9:39 a.m.
Jason T. Greene wrote:
In reality there is nothing wrong with [underscores],
they just aren't allowed in DNS.
That was correct in ARPANET times, but it's been untrue for
quite a while, even before internationalized domain names
became widely supported. DNS itself (as in the RFCs) does
not make such a restriction. Certain overly conservative
client programs may.
http://www.faqs.org/rfcs/rfc2181.html section 11:
"Implementations of the DNS protocols must not place any
restrictions on the labels that can be used."
or
http://www.faqs.org/rfcs/rfc3696.html section 2:
"Any characters, or combination of bits (as octets), are
permitted in DNS names."
Jonathan.
--
------------------------------------------------------------
Registered Address: Red Hat UK Ltd, Amberley Place, 107-111
Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom.
Registered in UK and Wales under Company Registration No.
3798903 Directors: Michael Cunningham (USA), Charlie Peters
(USA) and David Owens (Ireland)
9:58 a.m.
Jonathan Halliday wrote, On 10/11/2007 05:39 PM (EEST):
Jason T. Greene wrote:
> In reality there is nothing wrong with [underscores],
> they just aren't allowed in DNS.
That was correct in ARPANET times, but it's been untrue for quite a
while, even before internationalized domain names became widely
supported. DNS itself (as in the RFCs) does not make such a restriction.
Certain overly conservative client programs may.
Try to register one...
http://www.faqs.org/rfcs/rfc2181.html section 11:
"Implementations of the DNS protocols must not place any restrictions on
the labels that can be used."
or
http://www.faqs.org/rfcs/rfc3696.html section 2:
"Any characters, or combination of bits (as octets), are permitted in
DNS names."
Jonathan.
1:18 p.m.
Aleksandar Kostadinov wrote:
Jonathan Halliday wrote, On 10/11/2007 05:39 PM (EEST):
> Jason T. Greene wrote:
>> In reality there is nothing wrong with [underscores],
>> they just aren't allowed in DNS.
> That was correct in ARPANET times, but it's been untrue for quite a
> while, even before internationalized domain names became widely
> supported. DNS itself (as in the RFCs) does not make such a restriction.
> Certain overly conservative client programs may.
Try to register one...
lol. Actually this corner case is a great way of confusing
the customer support staff at most domain registrars. The
reasons this registration is more or less impossible at
present are somewhat convoluted. Warning: trivia ahead...
International domains names (IDNs) are basically anything
that contains values other than those allowed under the LDH
rule, which is as follows (rfc3696 section 2):
"The LDH rule, as updated, provides that the labels (words
or strings separated by periods) that make up a domain name
must consist of only the ASCII [ASCII] alphabetic and
numeric characters, plus the hyphen. No other symbols or
punctuation characters are permitted, nor is blank space.
If the hyphen is used, it is not permitted to appear at
either the beginning or end of a label. There is an
additional rule that essentially requires that top-level
domain names not be all-numeric."
So LDH is basically a real subset of ASCII. This becomes
important later.
International domains are not stuffed into the DNS in
unicode, even though it allows arbitrary octets, because
that would be way too straightforward and may break really
ancient clients that can only deal with LDH values.
Instead, the unicode value is transformed into an ACSII
Character Encoded (ACE) string, which is what actually gets
written into DNS. This approach was cooked up by ITEF and
Verisign (home of .com and .net). Most other registries
followed their lead. A browser plugin deals with taking what
the user types and converting it to an ACE value before
handing it off to the resolver library, which therefore does
not need to be IDN aware.
Here is the catch: The specific ACE algorithm they chose
does not translate the '_' character. It's valid ASCII, so
it goes through unaltered. Indeed, the output string is
valid ACSII so arguably the ACE is doing its job.
However, the output string is not a valid under the LDH
rule. So it can't go into the DNS as long as the registry's
policy remains to keep using only LDH.
Arggggg. So you can register domains with weird unicode
characters nobody in their right mind would use, but only if
the chosen ACE can encode them not only to ACSII but
specifically to LDH. But the ACE is not LDH aware, so it
doesn't always do that. Basically inputs that have any
character that is ACSII but not LDH may have problems,
whilst unicode values outside the ACSII range are fine. Oops.
Things get really interesting where the second level domain
is an IDN using LDH but the host part at the third level is
genuine unicode value that has not been through an ACE.
That's possible in cases where an organization is running
its own DNS servers for the third level, whilst the second
level is on .com registry public servers.
The resulting interaction between the browser plugin (which
is ACE encoding the entire name, host+domain), the client
resolver library (which may or may not be ACE and unicode
aware) and the various DNS servers, which may or may not be
operating recursively and may or may not each variously be
ACE and/or uincode aware, has the potential to be rather
messy to say the least. Interesting times ahead as this
becomes more prevalent I think.
Not that DNS was exactly straightforward to start with:
http://www.ccc.de/congress/2004/fahrplan/files/297-black-ops-of-dns-slide...
Jonathan.
--
------------------------------------------------------------
Registered Address: Red Hat UK Ltd, Amberley Place, 107-111
Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom.
Registered in UK and Wales under Company Registration No.
3798903 Directors: Michael Cunningham (USA), Charlie Peters
(USA) and David Owens (Ireland)
10:01 a.m.
Jonathan Halliday wrote:
Jason T. Greene wrote:
> In reality there is nothing wrong with [underscores],
> they just aren't allowed in DNS.
That was correct in ARPANET times, but it's been untrue for quite a
while, even before internationalized domain names became widely
supported. DNS itself (as in the RFCs) does not make such a restriction.
Certain overly conservative client programs may.
Yeah I was generalizing. BIND enforced it up to version 8. V9 changed
it, and will if check_names is explicitly enabled. Internic won't let
you register domains with it
--
Jason T. Greene
JBoss, a division of Red Hat
10:21 a.m.
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
>
--
Jason T. Greene
JBoss, a division of Red Hat
1:43 a.m.
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.
-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."
6:19 a.m.
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.
Yes, but you can still escape the hostname
*before* creating the jmx
service name surely?
-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
--
Tim Fox
Messaging lead
JBoss - a division of Red Hat
7:49 a.m.
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
--
Tim Fox
Messaging lead
JBoss - a division of Red Hat
8:04 p.m.
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
8:15 p.m.
Tim,
You should get a clean boot with:
cp server/default/lib/jmx-remoting.jar lib/endorsed
Although what we really need to do is create a special JSE jar that
contains only the classes we really want to override.
Jason T. Greene wrote:
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
8:16 p.m.
Sorry, I meant jboss-jmx-remoting.jar
Jason T. Greene wrote:
Tim,
You should get a clean boot with:
cp server/default/lib/jmx-remoting.jar lib/endorsed
Although what we really need to do is create a special JSE jar that
contains only the classes we really want to override.
Jason T. Greene wrote:
> 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
5:47 a.m.
Section 2 of RFC 3696 is also an interesting read.
Jonathan.
Carlo de Wolf wrote:
http://en.wikipedia.org/wiki/Hostname :
"Underscore characters are commonly used by Windows systems but
according to RFC 952 they are not allowed and several systems, such as
DomainKeys and the SRV record deliberately use the underscore to make
sure their special domain names are not confused with a hostname."
So we can add AS 5 to the list.
Carlo
On Wed, 2007-10-10 at 11:31 +0100, Tim Fox wrote:
> Just tried to start JB5 on my laptop, and it fails.
>
> Seems like something in remoting doesn't like hostnames with an
> underscore in them?
>
> My hostname is "tims_laptop".
>
> AS 4.x starts fine on the same machine.
>
> 11:05:17,197 ERROR [AbstractKernelController] Error installing to Start:
> name=jboss.remoting:protocol=rmi,service=JMXConnectorServer state=Create
> mode=Manual requiredState=Installed
> 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)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
>
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
> at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
> at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
> at
> org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> at
> org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
> at
> org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:184)
> at $Proxy4.start(Unknown Source)
> at
>
org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:42)
> at
>
org.jboss.system.microcontainer.ServiceControllerContextAction.install(ServiceControllerContextAction.java:46)
> at
>
org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
> at
>
org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327)
> at
>
org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:239)
> at
>
org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309)
> at
>
org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734)
> at
>
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862)
> at
>
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784)
> at
> org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:622)
> at
> org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411)
> at
> org.jboss.system.ServiceController.doChange(ServiceController.java:659)
> at
> org.jboss.system.ServiceController.start(ServiceController.java:431)
> at
> org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:149)
> at
> org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:107)
> at
> org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:46)
> at
>
org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.deploy(AbstractSimpleRealDeployer.java:65)
> at
>
org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169)
> at
>
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:728)
> at
>
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:749)
> at
> org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:669)
> at
>
org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327)
> at
>
org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309)
> at
>
org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734)
> at
>
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862)
> at
>
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784)
> at
> org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:622)
> at
> org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411)
> at
> org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:495)
> at
> org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:354)
> at
>
org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:245)
> at
>
org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:131)
> at
> org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:382)
> at org.jboss.Main.boot(Main.java:210)
> at org.jboss.Main$1.run(Main.java:529)
> at java.lang.Thread.run(Thread.java:595)
> 11:05:17,203 ERROR [AbstractKernelController] Error installing to Real:
>
name=vfsfile:/home/tim/dev/jbas/trunk/build/output/jboss-5.0.0.Beta3/server/default/deploy/jmx-remoting.sar/
> state=PostClassLoader mode=Manual requiredState=Real
> org.jboss.deployers.spi.DeploymentException: Error deploying:
> jboss.remoting:service=JMXConnectorServer,protocol=rmi
> at
>
org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
> at
> org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:126)
> at
> org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:46)
> at
>
org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.deploy(AbstractSimpleRealDeployer.java:65)
> at
>
org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169)
> at
>
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:728)
> at
>
org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:749)
> at
> org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:669)
> at
>
org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327)
> at
>
org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309)
> at
>
org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734)
> at
>
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862)
> at
>
org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784)
> at
> org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:622)
> at
> org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411)
> at
> org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:495)
> at
> org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:354)
> at
>
org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:245)
> at
>
org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:131)
> at
> org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:382)
> at org.jboss.Main.boot(Main.java:210)
> at org.jboss.Main$1.run(Main.java:529)
> at java.lang.Thread.run(Thread.java:595)
>
>
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
--
------------------------------------------------------------
Registered Address: Red Hat UK Ltd, Amberley Place, 107-111
Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom.
Registered in UK and Wales under Company Registration No.
3798903 Directors: Michael Cunningham (USA), Charlie Peters
(USA) and David Owens (Ireland)
6283
days inactive
6287
days old
jboss-development@lists.jboss.org
30 comments
10 participants
participants (10)
-
Aleksandar Kostadinov -
Ales Justin -
Carlo de Wolf -
Dimitris Andreadis -
Jason T. Greene -
Jonathan Halliday -
Ron Sigal -
Sacha Labourey -
Thomas Heute -
Tim Fox