[jboss-jira] [JBoss JIRA] (AS7-5409) CLONE - Unable to disable -Djava.net.preferIPv4=true in domain mode without editing domain.conf
Brian Stansberry (JIRA)
jira-events at lists.jboss.org
Tue Aug 21 15:26:15 EDT 2012
[ https://issues.jboss.org/browse/AS7-5409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Stansberry moved JBPAPP-9726 to AS7-5409:
-----------------------------------------------
Project: Application Server 7 (was: JBoss Enterprise Application Platform)
Key: AS7-5409 (was: JBPAPP-9726)
Workflow: GIT Pull Request workflow (was: jira)
Affects Version/s: 7.1.2.Final (EAP)
(was: EAP 6.0.0 ER 5)
Release Notes Docs Status: (was: Documented as Known Issue)
Release Notes Text: (was: If you use a command-line argument to bind to an IPv6 address at start-up, the server fails to start with the default configuration. The preferred workaround is to set the bind address in the configuration file, either <filename>domain.xml</filename> or <filename>standalone.xml</filename>. If you need to pass the IP address on the command line, add the <code>java.net.preferIPv4Stack=false</code> setting to your command. The following is an example of such a command.)
Component/s: Domain Management
(was: System)
(was: Documentation)
(was: Server boot)
Security: (was: Public)
Fix Version/s: 7.1.3.Final (EAP)
7.2.0.Alpha1
(was: TBD EAP 6)
Docs QE Status: (was: NEW)
> CLONE - Unable to disable -Djava.net.preferIPv4=true in domain mode without editing domain.conf
> -----------------------------------------------------------------------------------------------
>
> Key: AS7-5409
> URL: https://issues.jboss.org/browse/AS7-5409
> Project: Application Server 7
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 7.1.2.Final (EAP)
> Reporter: Jan Martiska
> Assignee: Brian Stansberry
> Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1
>
>
> Try running EAP domain mode like this:
> {noformat}
> bin/domain.sh -Djava.net.preferIPv4Stack=false -bmanagement=::1
> {noformat}
> It will fail:
> {noformat}
> [Host Controller] 09:40:49,647 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.network.management: org.jboss.msc.service.StartException in service jboss.network.management: JBAS015810: failed to resolve interface management
> [Host Controller] at org.jboss.as.server.services.net.NetworkInterfaceService.start(NetworkInterfaceService.java:97) [jboss-as-server-7.1.1.Final-redhat-1.jar:7.1.1.Final-redhat-1]
> [Host Controller] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1]
> [Host Controller] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1]
> [Host Controller] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_30]
> [Host Controller] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_30]
> [Host Controller] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30]
> {noformat}
> Other interfaces work and can be bound to ipv6, just 'management' does not. (In standalone mode, this issue is not present.)
> Blocks testing of Admin console,Native+HTTP interfaces in domain mode in IPv6, not marking as blocker because workaround exists.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list