[
https://issues.redhat.com/browse/WFLY-13805?page=com.atlassian.jira.plugi...
]
Brian Stansberry commented on WFLY-13805:
-----------------------------------------
I don't see how this is a WildFly issue. Our standard configs let you use a generic
java process configuration mechanism, -D, to let you set the bind address. If that somehow
doesn't work in Eclipse that's an Eclipse issue.
If Eclipse isn't using our standalone.sh script to start the java process but is
instead directly launching the JVM, as long as it either passes
-Djboss.bind.address={{<IP>}} to the JVM launch or passes it as an arg to our main,
it should work.
Bind address of Wildfly cannot be passed with Eclipse Runtime
-------------------------------------------------------------
Key: WFLY-13805
URL:
https://issues.redhat.com/browse/WFLY-13805
Project: WildFly
Issue Type: Enhancement
Affects Versions: 18.0.1.Final
Reporter: Andre Kreienbring
Assignee: Brian Stansberry
Priority: Major
This solution
[
https://access.redhat.com/solutions/18664]
says that one must pass the bind address with the start up command. And YES that works.
But because neither adding
{{{{<interface name="public">
<inet-address value="${jboss.bind.address:<IP>}"/>}}}}
{{{{}}{{ </interface>}}}}
to standalone.xml
nor passing -Djboss.bind.address={{{{<IP>}}}} in the Eclipse Launch Configuration
(JAVA Options) works, I'm obviously not able to start the server with a specific bind
address from Eclipse. It's only running on localhost and 127.0.0.1.
This is annoying for example during the development of a mobile app. The server simply
can't be reached when started with Eclipse.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)