FreeKB - How to start and stop TC Server JVM
How to start and stop TC Server JVM

Home > Search > How-to


tcruntime-ctl.sh script / tcserver command

Based on the version of TC Server that is installed, you will either use the tcruntime-ctl.sh script or the tcserver command to start, stop, restart, and check the status of a TC Server JVM. 

In this example, the tcruntime-ctl.sh script is used to start a JVM. This script can be run from the directory that contains the JVM, like this:

$CATALINA_HOME/your_profile/bin/tcruntime-ctl.sh start

 

Or from the install root directory of TC Server, like this:

~]$ $CATALINA_HOME/bin/tcruntime-ctl.sh start your_jvm

 

In this example, the tcserver command is used to start a JVM. 

$CATALINA_HOME/bin/tcserver start your_jvm

 

By default, the $CATALINA_HOME/instances directory will be used. If your JVMs are in any other directory, use the -i option.

$CATALINA_HOME/bin/tcserver start -i /path/to/your/instances your_jvm

 


Log files

catalina.out should show that the JVM was started.

mm dd, yyyy hh:mm:ss org.apache.catalina.startup.Catalina start
INFO: Server startup in 23615 ms

 

catalina.log should show that the Catalina service was started.

dd-mm-yyyy hh:mm:ss.sss INFO [Thread] org.apache.catalina.core.StandardService.startInternal Starting service [Catalina]

 

There will also be a file created that contain the PID associated with the JVM. The contents of this file will contain the PID.

[yyyy-mm-dd_hh:mm:ss] Using CATALINA_PID: /path/to/tcserver.pid

 

If the JVM contains one or more WARs, the catalina.log file can be used to ensure the WAR was deployed at startup.

mm dd, yyyy hh:mm:ss org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive example.war

 


Slow Startup

If a JVM is taking a while to startup, check the catalina.out / catalina.log files for long startup times. In this example, the creation of the SecureRandom session ID is taking a while. Usually, the SecureRandom session ID generation should take no more than 10,000 milliseconds.

org.apache.catalina.util.SessionIdGeneratorBase.createSecureRandom Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [2,746,205] milliseconds.

 

In this scenario, if the java.security files has "/dev/random", update java.security to have "/dev/urandom". 



Add a Comment




We will never share your name or email with anyone. Enter your email if you would like to be notified when we respond to your comment.




Please enter in the box below so that we can be sure you are a human.




Comments