Farewell to the annoying cmd window-running tomcat in the background and annoying cmd window tomcat

Farewell to the annoying cmd window-running tomcat in the background and annoying cmd window tomcat

The new project is about to be launched. This is the first project that you are responsible for, from development to implementation.

As soon as I got online, my mind would naturally imagine how I went to the client to get him xxxxxxx and so on. The process was first passed in my mind. In fact, I was familiar with installation and deployment, it's just a little nervous for the first time ~

When I thought about it, I thought that I could not mount a dos window to start tomcat for the customer. It was so ugly that the customer was definitely not satisfied (although they generally did not operate on servers ). What should we do? The background must be started.

It is understood that the user is using the windows system, so I went to check how to start tomcat in the background in windows. The record is as follows:

The core idea is to register tomcat as a windows system service and set it to auto start. Then OK ~

The specific registration is also performed using a service. bat provided under the tomcat bin directory. However, many problems may occur during this process:

Problem 1. No service. bat is found in the bin directory.

This should be a problem with the tomcat version. The standard version of tomcat on the official website does not contain service. bat (that is, it is named as apache-tomcat-6.0.41)

While tomcat with specific OS information contains this file (named like a apache-tomcat-6.0.41-windows-x86)

Problem 2: failed to install

Run cmd as an administrator and then run service install tomcat6.

When The call succeeds, The message "The service 'initat6' has been installed!" is displayed!

Problem 3: the service is successfully registered, but an error will be reported during startup:Windows cannot start Apache Tomcat on a local computer. For more information, see System Event Logs. If this is a non-Microsoft Service, contact the service provider and refer to the error code 0 for specific services.

The answer is:

The tomcat file path contains a Chinese directory

Copy msvcr71.dll under BIN in JDK to BIN in TOMCAT

Copy msvcr71.dll to the system32 directory

However, I found that none of the above methods is applicable to me.

It was found that the 32-bit tomcat was used on the 64-bit system. After the 64-bit tomcat was changed, everything was solved ~

But isn't the 64-bit system backward compatible? I wonder why this problem occurs ~