Is your feature request related to a problem? Please describe.
As a system administrator, I want REST APIs to listen on specific IP adress instead of port numbers to separate them. Current implementation allows to either listen on all(0.0.0.0) or single IP. This doesn't work well with eureka registration as it expects unique combination of host+port.
Describe the solution you'd like
Allow multiple API ML instances to listen on the same host+port and keed them all registered. Main goal is to support hot-standy mode in DVIPA and API ML to listen on DVIPA address. JGROUPS should still use LPAR hostname for cache.
Is your feature request related to a problem? Please describe.
As a system administrator, I want REST APIs to listen on specific IP adress instead of port numbers to separate them. Current implementation allows to either listen on all(0.0.0.0) or single IP. This doesn't work well with eureka registration as it expects unique combination of host+port.
Describe the solution you'd like
Allow multiple API ML instances to listen on the same host+port and keed them all registered. Main goal is to support hot-standy mode in DVIPA and API ML to listen on DVIPA address. JGROUPS should still use LPAR hostname for cache.