It is said that Tomcat 5.0.28 is the most stable tomcat. It was verified a few days ago that it ran 800 concurrent jobs on a machine that could only run 1200 concurrent jobs. After a day and a whole day, it went far away. Haha open-mouthed
However, there is a very serious problem. After Windows Service installer is installed under 64-bit Windows Server 2003 SP2 Enterprise Edition, an error is reported when the tomcatmonitor is used to start the service, and the service cannot start either. Tomcat can also be switched on. Use/bin/startup. bat is fine, but it is so uncomfortable that you have to log on, and the system cannot be restored automatically after the program fails, so you will not be able to enjoy the benefits of the system service. It seems that the ultimate solution is to start as a service.
Open event log. Based on the error message, the error return code is 0x0, which is meaningless. I searched the error returned information online and did not find anything. Run the 64-bit install Tomcat as service on Windows Server 2003 keyword to search for Tomcat monitor. The problem is found to be caused by Tomcat monitor. You must click tomcat in 64-Bit mode to enable tomcat. The * 32 mark next to tomcat5w.exe opens the task manager, which seems to be a problem.
Failed, but Tomcat still has no expectation.
Something that can run in a 32-bit system does not light up in 64-Bit mode. It seems that Tomcat is incompatible with 64-Bit mode. The solution on the Internet is to use tomcat5w.exe. amd64 to rename and overwrite the original file. Going online, going to the Svn of apache.org, I couldn't find files suffixed with amd64. I carefully studied the directory structure, which was organized according to the standard SVN mode. I went to trunks and went all the way down, go to bin, where there are IA64 and amd64. It is strange that the Tomcat 5.exeand tomcat5w.exe of IA64 come back, and cannot run directly after overwriting. The system prompts that the platform is inconsistent and the system is dizzy, intel's platform cannot run the IA64 program, but is IA64 an Teng? The file under amd64 is returned, overwrite, or do not light tomcat. Check every tab. All the options are empty. No wonder you cannot start them. Overwrite the 32-bit tomcat5.exeand tomcat5w.exe, write down all the parameters, and fill in the corresponding 64-bit version. After a long wait, the service status is started And yeah! Open Task Manager, tomcat5.exeand tomcat5w.exe, and there is no * 32 identifier next to them. It seems that the 64-bit purebred application is successful!
Go to services. MSC and set the recovery at5 service to the first and second restart services. restart the computer for the third time. Tomcat also enjoys the benefits of system services.
:
Http://svn.apache.org/viewvc/tomcat/tc6.0.x/tags/TOMCAT_6_0_16/res/procrun/amd64/