Restart service and Tomcat was logging without problem. It was sufficient to add and config.file. Somebody who was registering the service just omitted those lines when overriding –JvmOptions. file=C:\projects\apache-tomcat-7.0.40\conf\logging.properties
When I compared working service and Tomcat service without logging I found that following lines were missing: = This issue had nothing to do with stuff displayed in Logging tab. The tricky part here was not to check the Logging tab. It was necessary to open Tomcat service properties (ES stands for Edit Service): tomcat7w.exe \\ES\\tomcatweb The only difference was in the Tomcat’s start method. But there is a way through which we can create this service manually by writing a Systemd script. After several attempts to locate the bug I realized that Tomcat started by startup.bat was working correctly. The problem which arises is that it becomes difficult to start, stop or restart the Tomcat service as there is to service file installed, through which we could have easily used the command service tomcat start to start the service. There was no difference between directories of problematic Tomcat and working Tomcat. NOTE: If the Task Manager Services does not restart, it could be due to the time it takes for Stop to finish. Locate and select IDM Apps Tomcat Service and right-click, then select Start, Stop, or Restart. Tomcat downloaded from Apache’s website was creating logs without problem. Open Task Manager, and select More details if not already expanded. The only log produced by Tomcat was stdout and stderr from procrun wrapper. Tomcat installed as Windows service was not creating logs. This will run the script at reboot as well, assuming you have the scripts startup.sh and shutdown.sh in your home directory and you defined the environment variable correctly.I was chasing one very insidious bug. sudo ln -s /etc/init.d/shutdown.sh /etc/rc6.d/K04shutdown.sh I don't know java so i just left the export statements there, doesn't matter. Save it then sudo chmod a+x //shutdown.shĪnd make a symbolic link of that to /etc/rc0.d/ sudo ln -s /etc/init.d/shutdown.sh /etc/rc0.d/K04shutdown.sh Is it a headless server? I had that issue with a headless server I chose a lazy solution of just adding the code to /etc/rc.local: export JAVA_HOME=/usr/local/java/jdk1.8.0_05Įxport CATALINA_HOME=/ubuntuland/utils/apache-tomcat-8.0.8Īnd make a script with this code in /etc/init.d/shutdown.sh export JAVA_HOME=/usr/local/java/jdk1.8.0_05
0 kommentar(er)
