Bug 760789 - ESB resources are no longer valid after upgrading
Summary: ESB resources are no longer valid after upgrading
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: RHQ Project
Classification: Other
Component: Plugins
Version: 3.0.1
Hardware: All
OS: All
urgent
urgent vote
Target Milestone: ---
: ---
Assignee: Len DiMaggio
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-06 23:59 UTC by Larry O'Leary
Modified: 2018-11-14 09:41 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
JBoss ON w/ SOA-P Plug-in Pack (ESB)
Last Closed: 2013-09-04 13:47:41 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Larry O'Leary 2011-12-06 23:59:10 UTC 
The ESB plug-in included in JON 2.4.1 has renamed many of the ESB resource types. The result is that ESB resources that existed in inventory prior to the upgrade will become invalid and "unknown" to the JON agent resulting in inventory sync failures for these resources.
Comment 1 John Mazzitelli 2011-12-08 14:55:43 UTC 
This appears related to https://issues.jboss.org/browse/JBESB-3110
Comment 2 John Mazzitelli 2011-12-08 15:33:39 UTC 
Here are the different names that I've found from prior versions:

from plugin pack "jon-plugin-pack-soa-2.4.0.GA.jar", specifically the plugin named "rhq-jbossesb-soa-plugin-SOA.4.3.0.GA_CP02.jar"

<plugin name="JBossESB" version="2.0"
JBoss ESB Deployment
JBoss ESB Services
JBoss ESB Listeners

In all other ESP plugins, the names for those resource types are:

Deployment
Services
Listeners

This means when upgrading from SOA 4.3.0 plugin that shipped with JON 2.4.0 to any later version, old resources of those types will be unavailable.
Comment 3 Charles Crouch 2011-12-09 16:17:54 UTC 
Assigning to Len D, to investigate.
Comment 8 Heiko W. Rupp 2013-09-04 08:46:26 UTC 
Larry can we close this, as it is pretty old?
Comment 9 Larry O'Leary 2013-09-04 13:47:41 UTC 
As this is something that happened during upgrade on a a now unsupported version of JBoss ON and was only reported by one person I will go ahead and close this issue as WONTFIX.
Note You need to log in before you can comment on or make changes to this bug.