[jboss-jira] [JBoss JIRA] Commented: (AS7-1039) AS fails to boot if hostname is not pingable
Georges Berscheid (JIRA)
jira-events at lists.jboss.org
Wed Aug 24 04:24:18 EDT 2011
[ https://issues.jboss.org/browse/AS7-1039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12623637#comment-12623637 ]
Georges Berscheid commented on AS7-1039:
----------------------------------------
The problem seems to be here:
org.jboss.as.process.Main:216
configuration.setBindAddress(new InetSocketAddress(InetAddress.getLocalHost(), 0));
It tries to bind a listening socket to the IP address that the hostname resolves to. If it doesn't resolve to anything, or worse, resolves to an IP address that's not assigned to any interface on the host (e.g. the public address in a NATed network).
The line above should either be removed to make the --bind-addr and --bind-port options available again or use 0.0.0.0 as a default to listen on all available interfaces.
> AS fails to boot if hostname is not pingable
> --------------------------------------------
>
> Key: AS7-1039
> URL: https://issues.jboss.org/browse/AS7-1039
> Project: Application Server 7
> Issue Type: Bug
> Components: Server
> Affects Versions: Open To Community
> Environment: Fedora 15
> Reporter: Misty Stanley-Jones
> Fix For: Open To Community
>
>
> If hostname is not pingable (such as a made-up value like "cheezel" or a FQDN like "dhcp-111-bne.redhat.com"), the AS fails to start in domain mode, with a bindException. If I change the hostname to "localhost", the AS starts fine.
> AS starts in standalone mode regardless.
> See the error at http://fpaste.org/xawH/.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list