ETS Insides automatically selects the listening tcp port, starting from 8080 and counting up if the port is already in use. This behavior leads to some problems:
- If there is another service on the same machine requiring port 8080 (like Tomcat or Apache) you get a race condition. If the other daemon is started first, everything will be fine. If ETS Inside is already running, it takes port 8080 and the other application will crash.
- The behavior makes it difficult to define strict incoming firewall rules, because after a crash or restart the service might be running on another port than before.
Please add a configuration file or command line option that allows to define a fixed port that ETS Inside should be listening to.
Vous devez vous connecter pour laisser un commentaire.