Tomcat cannot shutdown after enabling monitoring via jmx

[frlan]

Hi folks,

I'm posting here as might someone can help me out. for monitoring a tomcat I've added based on http://www.zabbix.com/documentation/...jmx_monitoring

-Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=12345
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false

to my catalina.sh which is called by startup.sh.

Unfortunately now shutdown.sh, which also refers to catalina.sh is complaining, that port 12345 is already in use. (which I understand as it is). But What's the correct (read: TOMCAT-way) way to add the options to startup.sh so shutdown.sh is still working?

[sneha.bhat]

Weblogic server monitoring in zabbix 2.0

Hello All,

We want to monitor a Weblogic Server via Zabbix 2.0. For this we want to utilize the new jmx monitoring feature that has been added into zabbix. To configure this we have carried out the following steps:

1. Created a host for the server
2. Added a JMX interface which communicates on port 10052
3. On the Weblogic front we have added the parameter to enable remote jmx in the SetDomainEnv.sh file which is called during start up.

JAVA_OPTIONS="$JAVA_OPTIONS -Dcom.sun.management.jmxremote=true"
JAVA_OPTIONS="$JAVA_OPTIONS -Dcom.sun.management.jmxremote.port=10052"
JAVA_OPTIONS="$JAVA_OPTIONS -Dcom.sun.management.jmxremote.ssl=false"
JAVA_OPTIONS="$JAVA_OPTIONS -Dcom.sun.management.jmxremote.authenticate=false"

4. The Weblogic server is getting started after addition of these parameters and we are also able to telnet on port 10052

But the JMX interface is not getting enabled on the ports. Its throws a "ZBX_TCP_READ() failed: [4] Interrupted system call" error. No value is coming for any parameter through zabbix_get. We have attached a JMX Generic template to the host as of now. But no items are collected any data.

Would appreciate any kind of help of this and on keys of items to be monitored for the weblogic server.

[awienber]

tomcat JMX options

But What's the correct (read: TOMCAT-way) way to add the options to startup.sh so shutdown.sh is still working?

The correct way AFAIK is to add them to CATALINA_OPTS in setenv.sh.

It seems that in your case, the small java program which is supposed to shut down tomcat also tries to open the same JMX port. By setting the system property in CATALINA_OPTS, the port will only be used for the tomcat process itself, not the shutdown helper.

Regards,
Axel