Bug 779574 (SOA-1949)

Summary:	ESB plugin needs to be renamed - to support running 4.3 and 5.0 simultaneously
Product:	[JBoss] JBoss Enterprise SOA Platform 5	Reporter:	Jaroslaw Kijanowski <kijanowski>
Component:	Monitoring and Management	Assignee:	Julian Coleman <jcoleman>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	5.0.0 CR1	CC:	dlesage
Target Milestone:	---
Target Release:	5.0.2
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/SOA-1949
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-08-05 11:01:54 UTC	Type:	Task
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Jaroslaw Kijanowski 2010-02-12 19:52:48 UTC

Affects: Release Notes
Date of First Response: 2010-02-16 19:54:56
project_key: SOA

It's not possible to run the ESB plugin for SOA-P 4.3 and SOA-P 5 side by side. The JON server will remove the older plugin:

2010-02-12 11:06:57,514 INFO [org.rhq.enterprise.server.core.plugin.AgentPluginDeploymentScanner] Deleted an obsolete plugin file: /qa/services/hudson/jkijanow/CR1/jon-server-2.3.0.GA/jbossas/server/default/deploy/rhq.ear/rhq-downloads/rhq-plugins/rhq-jbossesb-soa-plugin-SOA.4.3.0.GA_CP01.jar

To have it running successfully I've renamed the the SOA 5 plugin in META-INF/rhq-plugin.xml
from "JBossESB" to "JBossESB50"

Comment 1 Jaroslaw Kijanowski 2010-02-12 19:55:55 UTC

Link: Added: This issue depends JBESB-3181

Comment 2 Jaroslaw Kijanowski 2010-02-16 22:03:19 UTC

Hey David, can you add this to the release notes? It won't be fixed for GA.
The consequence of this issue is that you cannot use the same JON server and agent to manage SOA instances with different versions (4.3 and 5.0). JON will remove the older esb plugin and you won't be able to manage SOA-P 4.3.
So either you use the SOA 4.3 plugin to manage SOA 4.3 or you use the SOA 5 plugin to manage SOA 5. A workaround, which allows you to manage both instances at the same time is provided in comments above (rename the plugin name).

Comment 3 Jaroslaw Kijanowski 2010-02-16 22:04:06 UTC

Affects: Added: [Release Notes]

Comment 4 David Le Sage 2010-02-17 00:54:56 UTC

Hello Jaroslaw,

Thanks for the detailed explanation of the bug - that is really appreciated at our end.  :-)


Here is the draft text in the Release Notes:


https://jira.jboss.org/jira/browse/SOA-1949

    Currently, you cannot run the ESB plug-ins for both SOA-P 4.3 and SOA-P 5 simultaneously  The JON Server will automatically remove the plug-in for the older release. As a result, you cannot use the same JON server and agent to run different versions of SOA.

    To work around this issue, rename the SOA-P 5 plug-in (in META-INF/rhq-plugin.xml) from
    "JBossESB" to "JBossESB50."

Comment 5 Jaroslaw Kijanowski 2010-02-17 09:25:33 UTC

Looks good, however looking at the rel notes here:
http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_SOA_Platform/5.0.0/html-single/Release_Notes/#id-release_notes-known_issues

and there is "... from *194* ...":
To work around this issue, rename the SOA-P 5 plug-in (in META-INF/rhq-plugin.xml) from 194"JBossESB" to "JBossESB50."

Comment 6 David Le Sage 2010-02-18 00:13:39 UTC

Thanks.  Fixed it up.

Comment 7 Jaroslaw Kijanowski 2010-02-18 09:56:56 UTC

Verified.

Comment 8 Jaroslaw Kijanowski 2010-02-19 07:47:26 UTC

Release notes are fine but this is still an open issue and should be fixed in the future.

Comment 9 Julian Coleman 2010-03-03 11:32:20 UTC

For the SOA 5 plugin, the following changes are needed to META-INF/rhq-plugin.xml:

  plugin name="JBossESB5"
        displayName="JBossESB5"
        description="Provides monitoring of JBoss ESB 5"