Listen on single IP address
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 92
- Forks
- 81
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 46
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the REST listener configuration and Eureka registration path, then review how JGroups derives its cache hostname. Done means multiple instances can share a host and port while registering distinct configured IPs, with DVIPA hot-standby support and JGroups still using the LPAR hostname.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100