Manager auto-detection fails when literal IPv6 addresses are used

Description

Customer has designed a solution that uses XAP. They will give their customer a configuration script, which will then be used to configure underlying applications such as XAP. A requirement is that they will only be using ipv6 literals, they will not be using hostnames.

Currently if XAP_MANAGER_SERVERS is set to ipv6 literal, then XAP will not start:
Error: java.lang.ExceptionInInitializerError host run-agent --manager --gsc=2 --webui

(Setting XAP_MANAGER_SERVERS to hostname works, but customer will only be using ipv6 literals)

Or:
2019-09-27 13:10:19,477 SEVERE [com.gigaspaces.start] - Error while booting system - ; Caused by: java.net.MalformedURLException: For input string: "0:0:0:e900:c19f:9b43:adbb:-1"

(-Djava.rmi.server.hostname=${HOSTNAME} makes this go away, but customer will only be using ipv6 literals.)

Setting the XAP_NIC_ADDRESS to an ipv6 literal works.

This behavior was tested with 15.0.0-m13.

Issue is not whether XAP works with ipv6, but being able to use ipv6 literal to set various configurations.

Workaround

None

Acceptance Test

Tested manually

Status

Assignee

Niv Ingberg

Reporter

Dixson Huie

Labels

None

Priority

Medium

SalesForce Case ID

12602

Fix versions

Commitment Version/s

None

Due date

None

Product

None

Edition

Open Source

Platform

All
Configure