Monitoring Tomcat6 with SCS

Hello,

We are trying to monitor the tomcat6 instance we installed using yum install. The following is what we have set:

In the Annex Options:
start_stop start_command /etc/init.d/tomcat6 start
start_stop stop_command /etc/init.d/tomcat6 stop

In the Server info:
Working Directory: /etc/init.d/
Command Line: tomcat6
Command Line Arguments: start

The application goes into pending status and then stops, but the service in the server is started, just not being shown by SCS as started. I did some reading of a similar case and it suggests Command Line and Command Line Arguments must match what is returned by ps -ef|grep catalina command.

I ran this and it returns a really long string that is over the limit allowed in these fields.

Any help would be appreciated.

The information within StartInfo tab has to be match with the path and arguments of running process. So, the path should not be like “/etc/init.d/ because, the Tomcat is not running there”. Try to list the running processes, find the Tomcat and copy the executable path and possible arguments to the Genesys configuration.

Hi Kubig,

Thank you very much for the response. Unfortunately the running process returns:

UID PID PPID C STIME TTY TIME CMD
tomcat 8655 1 6 11:02 ? 00:02:04 /srv/GCTI/Java7/bin/java -XX:MaxPermSize=2048m -Xms2048m -Xmx5120m -Djavax.sql.DataSource.Factory=org.apache.commons.dbcp.BasicDataSourceFactory -classpath :/usr/share/tomcat6/bin/bootstrap.jar:/usr/share/tomcat6/bin/tomcat-juli.jar:/usr/share/java/commons-daemon.jar -Dcatalina.base=/usr/share/tomcat6 -Dcatalina.home=/usr/share/tomcat6 -Djava.endorsed.dirs= -Djava.io.tmpdir=/var/cache/tomcat6/temp -Djava.util.logging.config.file=/usr/share/tomcat6/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager org.apache.catalina.startup.Bootstrap start

Which is too long to input into the fields.

Genesys has a limit for path or argument length, so in this case, the monitoring of 3rd party application will not work.