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.
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/2109#2109
According to https://msdn.microsoft.com/en-us/library/windows/desktop/
> From: Igor Cicimov [mailto:icici...@gmail.com]
> Subject: Re: Under system account, Tomcat starts even with shutdown port
> conflict
> If you are trying to run it on port <1024 you need authbind enabled
Read the original message. The OP is running on Windows
If you are trying to run it on port <1024 you need authbind enabled
On 9 Jun 2017 1:21 am, "Tou Vue" wrote:
> Hello,
>
> I have a question regarding how Tomcat starts up under the system account
> and local user account in Windows. I had a Tomcat service that would start
>
Tomcat was able to access the same port if I turned off the other service.
So I don't think it's protected.
Thank You,
Tou Vue
On Thu, Jun 8, 2017 at 10:26 AM, Coty Sutherland
wrote:
> On Thu, Jun 8, 2017 at 11:21 AM, Tou Vue wrote:
> > Hello,
> >
> >
On Thu, Jun 8, 2017 at 11:21 AM, Tou Vue wrote:
> Hello,
>
> I have a question regarding how Tomcat starts up under the system account
> and local user account in Windows. I had a Tomcat service that would start
> fine under the system account, but once I configured it to
Hello,
I have a question regarding how Tomcat starts up under the system account
and local user account in Windows. I had a Tomcat service that would start
fine under the system account, but once I configured it to start under the
local user account, I received a JVM_Bind exception. I looks like