150
votes

Both Google and Stackoverflow have shown me people with similar issues however this error is slightly different in that the IP address is suffixed with an asterisk:

NetBeans 8.0.1 is giving me the following error when trying to start Tomcat.

'127.0.0.1*' is not recognized as an internal or external command, operable program or batch file.

I've got both Tomcat 7.0.56 and Tomcat 8.0.14 installed, they both start OK from the command line (one at a time). I have them added to NetBeans' list of servers as Tomcat 7 and Tomcat 8.

I have a "Hello World" web app which I have configured:
Properties -> Run -> Server: tried both Tomcat 7 and Tomcat 8
Both give the same error.

If I try starting Tomcat using either:
Services -> Servers -> Tomcat 7 -> Start
Services -> Servers -> Tomcat 8 -> Start
I get the same error as when trying to start a web app:

'127.0.0.1*' is not recognized as an internal or external command, operable program or batch file.

Any ideas ?
Even if it's only what that asterisk is doing there ?

4
Possible duplicate of Starting of Tomcat failed from NetbeansYoYo
If you want to read deeper analysis on this bug, see my stackoverflow answer from 2015 here stackoverflow.com/questions/30647156/… It is for TomEE but it based on Tomcat so the same solution works here as well. Switching off the proxy settings in Netbeans also works of course as some others suggested.Miklos Krivan

4 Answers

379
votes

Assuming you are on Windows (this bug is caused by the crappy bat files escaping), It is a bug introduced in the latest versions (7.0.56 and 8.0.14) to workaround another bug. Try to remove the " around the JAVA_OPTS declaration in catalina.bat. It fixed it for me with Tomcat 7.0.56 yesterday.

In 7.0.56 in bin/catalina.bat:179 and 184

:noJuliConfig
set "JAVA_OPTS=%JAVA_OPTS% %LOGGING_CONFIG%"

..

:noJuliManager
set "JAVA_OPTS=%JAVA_OPTS% %LOGGING_MANAGER%"

to

:noJuliConfig
set JAVA_OPTS=%JAVA_OPTS% %LOGGING_CONFIG%

.. 

:noJuliManager
set JAVA_OPTS=%JAVA_OPTS% %LOGGING_MANAGER%

For your asterisk, it might only be a configuration of yours somewhere that appends it to the host declaration.

I saw this on Tomcat's bugtracker yesterday but I can't find the link again. Edit Found it! https://issues.apache.org/bugzilla/show_bug.cgi?id=56895

I hope it fixes your problem.

55
votes

After following the steps from @Johnride, I still got the same error.

This fixed the problem:

Tools-> Options-> Select no proxy

source: https://www.youtube.com/watch?v=uI1j-8F8eN4

9
votes

Tools-> Options-> Select no proxy is worked for me

0
votes

I didnt try Sumama Waheed's answer but what worked for me was replacing the bin/catalina.jar with a working jar (I disposed of an older tomcat) and after adding in NetBeans, I put the original catalina.jar again.