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