Description of problem:

Hi,

We have a tomcat resource agent configured in our pacemaker cluster like this:

  Resource: Tomcat (class=ocf provider=heartbeat type=tomcat)
   Attributes: tomcat_user=tomcat java_home=/usr/lib/jvm/jre-1.7.0 java_opts="-server -Xmx2048m" catalina_home=/usr/share/tomcat catalina_base=/usr/share/tomcat catalina_tmpdir=/var/cache/tomcat/temp logging_config=/usr/share/tomcat/conf/logging.properties logging_manager=org.apache.juli.ClassLoaderLogManager statusurl=http://localh
ost:8080/app/status 

This used to work fine, but since the upgrade to the latest tomcat package (security update) this no longer works.

Root cause seems to be that /usr/sbin/tomcat (which is used by the resource agent) now uses systemd to start tomcat. 

Regards,

Rik


Version-Release number of selected component (if applicable):


How reproducible:
tomcat-7.0.54-8.el7_2.noarch

Steps to Reproduce:
1. Configure pacemaker resource using the tomcat resource agent
2. Upgrade to latest tomcat package
3.

Actual results:
tomcat fails to start correctly

Expected results:
Tomcat works like before


Additional info: