rmannibucau commented on PR #857: URL: https://github.com/apache/tomcat/pull/857#issuecomment-2897864027
@markt-asf not really, the issue is really on tomcat side and its any handling at a time which is decoralated from the binding time. If using a specific interface there is no issue but with multiple interfaces tomcat just randomly assumes the family. The disable setting is something you can set at runtime so tomcat really has a bug between the bind logic and the shutdown logic there even if I can agree it is probably something rare (that said with kubernetes or net related config it is not rare this is a setting is also customized after startup with a (systemctl) service. So still think tomcat shouldn't just think it is fine but either collect the shutdown ip earlier (just after bind), enforce the family since java will do it anyway and it solves all issues or just hide the warn/error when shutting down since it knows it is fine cause the thread is no more alive anyway. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
