Loading...

XML

Word

Printable

Type: Bug
Resolution: Won't Do
Priority: Minor
Fix Version/s: None
Affects Version/s: 2.0.16.Final
Component/s: API
Labels:
None

Steps to Reproduce:

Hide

Setup: 1 PC 2 Network cards.

Set metric of Network-adapter1 to "1" using ip 123.123.123.123
Set metric of Network-adapter2 to "2" using ip 222.222.222.222

Open powershell and execute

ping (hostname) -4

You will get a 123.123.123.123.

Now start jboss using param -Djboss.bind.address=<hostname>.

JBoss will bind to address 222.222.222.222 !

This is a bug, the 123.123.123.123 has a lower metric and must be preferred.

Show
Setup: 1 PC 2 Network cards. Set metric of Network-adapter1 to "1" using ip 123.123.123.123 Set metric of Network-adapter2 to "2" using ip 222.222.222.222 Open powershell and execute ping (hostname) -4 You will get a 123.123.123.123. Now start jboss using param -Djboss.bind.address=<hostname>. JBoss will bind to address 222.222.222.222 ! This is a bug, the 123.123.123.123 has a lower metric and must be preferred.
Workaround:

Workaround Exists
Workaround Description:

Hide

Do not bind to hostname, always bind to IP-Address.

Show
Do not bind to hostname, always bind to IP-Address.

In windows we can have one hostname.
Furthermore we can have two Network Interfaces.
The Network Interfaces can have different IP-Addresses.
This means one hostname can have two different IP addresses!
What IP Address is preferred is defined by the "metric". Lower metrics must be preferred.

Bug: JBoss ignores the metric.

Assignee:: Bartosz Baranowski

Reporter:: Peter Rader (Inactive)

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Created:: 2018/12/03 12:33 PM

Updated:: 2021/07/23 9:02 AM

Resolved:: 2021/07/23 9:02 AM

Estimated:

Remaining:

Logged:

Not Specified

Details

Description

Attachments

Activity

People

Dates

Time Tracking