Bug 1005109

Summary:	Upgrading Tomcat plugin, metric names not updated
Product:	[Retired] JBoss Web Server 3	Reporter:	Thomas Segismont <tsegismo>
Component:	unspecified	Assignee:	Jean-frederic Clere <jclere>
Status:	CLOSED EOL	QA Contact:	Jan Stefl <jstefl>
Severity:	high	Docs Contact:
Priority:	high
Version:	3.0.0	CC:	genman, hrupp, jclere, mbabacek, myarboro, rmarwaha, spinder
Target Milestone:	Post-GA
Target Release:	3.0.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1005095	Environment:
Last Closed:	2020-03-27 19:36:37 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:	1005095
Bug Blocks:

Description Thomas Segismont 2013-09-06 09:00:09 UTC

+++ This bug was initially created as a clone of Bug #1005095 +++

Description of problem:
When upgrading a 4.5 and older RHQ installation, the Tomcat plugin is not updated.

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

How reproducible:
Always

Steps to Reproduce:
1. Install RHQ 4.5
2. Upgrade to RHQ 4.6 or newer

Actual results:
The Tomcat plugin is not updated

Expected results:
The Tomcat plugin is updated

Additional info:
The following exception is thrown:
java.lang.IllegalArgumentException: The property [name] marked as required in the configuration definition of [Tomcat Connector] has no attribute 'default'  

Reported by user in community forum:
https://community.jboss.org/message/836495?et=watches.email.thread#836495

Comment 1 Thomas Segismont 2013-09-06 09:11:23 UTC

In April Jean Frederic cherry-picked the RHQ master commit

commit bda985816a6cea4adc776c9a93d6b029ddcb7753
Author: jfclere <jfclere.redhat.com>
Date:   Wed Apr 10 14:33:38 2013 +0200

    fix for BZ: 707349 from e7d48240474fba87f1a3c4118de4618fd2c8b32d.


So JON 3.1.2 is not impacted but this shouldn't got out with JON 3.2

Comment 2 Heiko W. Rupp 2013-09-06 15:33:46 UTC

Jean-Frederic, can you please have a look at this. 

This community post is pretty detailed about the issue and a possible fix:

https://community.jboss.org/message/836495?et=watches.email.thread#836495

Thanks