RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1022792 - tomcat agent relies on catalina.sh which we don't ship
Summary: tomcat agent relies on catalina.sh which we don't ship
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: resource-agents
Version: 6.4
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: David Vossel
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-24 04:47 UTC by Andrew Beekhof
Modified: 2014-10-14 04:59 UTC (History)
6 users (show)

Fixed In Version: resource-agents-3.9.2-46.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-10-14 04:59:26 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:1428 0 normal SHIPPED_LIVE resource-agents bug fix and enhancement update 2014-10-14 01:06:18 UTC

Description Andrew Beekhof 2013-10-24 04:47:55 UTC 
Description of problem:

ocf:heartbeat:tomcat agent is hard coded to use a binary we don't ship

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

Version     : 3.9.2                             Vendor: Red Hat, Inc.
Release     : 21.el6_4.8                    Build Date: Mon 07 Oct 2013 16:13:15 EDT


How reproducible:

100%

Steps to Reproduce:
1. start cluster
2. yum install -y tomcat6 
3. pcs resource create tomcat6 tomcat java_home=/usr/lib/jvm/jre-1.6.0-openjdk.x86_64 catalina_home=/usr/share/tomcat6

Actual results:

Start fails

Expected results:

Start succeeds
Comment 2 David Vossel 2014-01-21 19:28:45 UTC 
Upstream fixes related to this issue have been merged.
https://github.com/ClusterLabs/resource-agents/pull/354

The heartbeat tomcat agent should be able to be supported in rhel6 now.
Comment 4 David Vossel 2014-04-22 21:58:54 UTC 
unit test.

# yum install -y tomcat6 tomcat6-webapps
# cd /usr/lib/ocr/resource.d/heartbeat/
# export OCF_ROOT=/usr/lib/ocf/ OCF_RESKEY_catalina_home=/usr/share/tomcat6 OCF_RESKEY_java_home=/usr/lib/jvm/jre-1.6.0  OCF_RESKEY_tomcat_start_script="/usr/sbin/tomcat6"

# ./tomcat monitor
# echo $?
# 7

# ./tomcat start
# echo $?
# 0

# ./tomcat monitor
# echo $?
# 0

# ./tomcat stop
# echo $?
# 0

# ./tomcat monitor
# echo $?
# 7
Comment 6 michal novacek 2014-04-28 14:54:14 UTC 
I have verified that the bug has been fixed and tomcat starts correctly with
resource-agents-3.9.2-47.elY6.x86_64.

BEFORE the fix: resource-agents-3.9.2-40.el6.x86_64
------
# ./tomcat status
tomcat instance tomcat is stopped

# ./tomcat stop
DEBUG: [tomcat] Enter tomcat stop
DEBUG: [tomcat] Leave tomcat stop 0

# ./tomcat start
DEBUG: [tomcat] Enter tomcat start
INFO: validate_all_tomcat[tomcat]
DEBUG: Tomcat port is 8080
DEBUG: grep port="8080" /usr/share/tomcat6/conf/server.xml
DEBUG: CATALINA_OPTS value = -Dname=tomcat
DEBUG: start_tomcat[tomcat]: retry monitor_tomcat
DEBUG: start_tomcat[tomcat]: retry monitor_tomcat
...


FIXED version: resource-agents-3.9.2-47.elY6.x86_64
-----
# ./tomcat status
tomcat instance tomcat is stopped

# ./tomcat stop
DEBUG: [tomcat] Enter tomcat stop
DEBUG: [tomcat] Leave tomcat stop 0

# ./tomcat start
DEBUG: [tomcat] Enter tomcat start
INFO: validate_all_tomcat[tomcat]
DEBUG: Tomcat port is 8080
DEBUG: grep port="8080" /usr/share/tomcat6/conf/server.xml
DEBUG: CATALINA_OPTS value = -Dname=tomcat 
DEBUG: start_tomcat[tomcat]: retry monitor_tomcat
DEBUG: Reading pid from /var/run/resource-agents/tomcat_tomcatstate/catalina.pid
DEBUG: Sending noop signal to 8433
DEBUG: [tomcat] Leave tomcat start 0
Comment 7 errata-xmlrpc 2014-10-14 04:59:26 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-1428.html
Note You need to log in before you can comment on or make changes to this bug.