The NIO transporter listens to the same host as the one configured in the topology.
It can be problematic if we want to listen to all ips of the machine (0.0.0.0).
The bottom of the issue is that we should differentiate between the listening ip and the host/ip used by other container to contact another one.
This also the case for the WS-API extension.
Concerning the Admin JMX service, it is a bit different because it is the RMI Registry that actually listens for both of them and it is not configurable to listen to specific interfaces: it will always listen to everything.
We should introduce thus new configurations in server.properties to specify the address to listen to (localhost, 0.0.0.0, 192.160.1.1, etc):
- petals.transport.tcp.receivers.listening.interface
- petals.ws-api.http.listening.interface
It will default to the host of the current container as declared in the topology!
Improvement Request
Resolved
Minor