Start a JVM
Let's say the name of your Pivotal TC Server instance is named myTCInstance. Use the following command to start your Pivotal TC Server.
~]$ $CATALINA_HOME/myTCInstance/bin/tcruntime-ctl.sh start . . . Tomcat started. Status: RUNNING as PID=12345
Ensure TC server is running.
~]$ $CATALINA_HOME/myTCInstance/bin/tcruntime-ctl.sh status . . . Status: RUNNING as PID=12345
The catalina.out file can also used to ensure the JVM was started.
mm dd, yyyy hh:mm:ss org.apache.catalina.startup.Catalina start INFO: Server startup in 23615 ms
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
Stop a JVM
Use the following command to stop the instance named myTCInstance.
~]$ $CATALINA_HOME/myTCInstance/bin/tcruntime-ctl.sh stop . . . Instance shut down gracefully
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".