You should still be consistent about how you start Tomcat in Windows. Look into reboot situations. Look into file permissions if your app writes any files. These are other places where you can get inconsistent results.
I've always used Ubuntu or Solaris in production to narrow these issues. Always worked with the project distros since Tomcat e. Regards, Dave Sent from my iPhone > On Jun 9, 2017, at 1:55 PM, Tou Vue <tvue0...@gmail.com> wrote: > > Found out this is working as designed. > > You can follow the link to where I answered my own question... > https://stackoverflow.com/questions/44400047/starting- > tomcat-with-local-user-causes-jvm-bind-exception/44442109#44442109 > > According to https://msdn.microsoft.com/en-us/library/windows/desktop/ > ms740621(v=vs.85).aspx > > If both application are in the same user context then both can bind to the > same port if one of the application is using the invalid address. (0.0.0.0) > > If both application are in different user context then we get the exception. > Thank You, > > *Tou Vue* --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
