why is my tomcat console dying just after starting up?
it sometime happens that when you start the CLM server (running on tomcat) you see a command line console appearing and then dies before you have time to read what the problem is, How can I trouble shoot this?
|
Accepted answer
the script used to start the CLM server, server.startup.bat will call a tomcat script startup.bat that will itself call catalina.bat.
you can start catalina.bat with different option, the default is set to start in startup.bat which will open the console in a new window. the details of the options are given in catalina.bat: echo debug Start Catalina in a debugger echo debug -security Debug Catalina with a security manager echo jpda start Start Catalina under JPDA debugger echo run Start Catalina in the current window echo run -security Start in the current window with security manager echo start Start Catalina in a separate window echo start -security Start in a separate window with security manager echo stop Stop Catalina echo configtest Run a basic syntax check on server.xml echo version What version of tomcat are you running? so edit startup.bat to use the "run" option and next time you start server.startup.bat in the server directory, tomcat will start in the same window. change: call "%EXECUTABLE%" start %CMD_LINE_ARGS% to call "%EXECUTABLE%" run %CMD_LINE_ARGS% you would then be able to see error such as: JVMJ9VM015W Initialization error for library j9gc24(5): Failed to allocate default memory space Could not create theJava virtual machine Ralph Schoon selected this answer as the correct answer
Comments In all the cases that I've seen with this symptom the problem is memory like the error message reports. To resolve the issue make sure the system meets the memory requirements. But as a workaround to get the server running until memory is acquired, lower the -xmx value in server.startup.bat. The default value is 4000 M.
Kevin Ramer
commented Apr 12 '13, 8:32 a.m.
While speaking of JVM, only a 64-bit JRE will allow that size for JVM parameters. I think 32bit max is 2048.
Nifty trick. I usually just run server.startup from the command-line to see the error.
Actually, I take that back. I just ran into this problem and I see that even running server.startup on the command-line can end up in a window appearing and immediately disappearing. Thanks for the tip!
|
One other answer
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.
Comments
Hi,