779085 – (SOA-1484) In JON 2.3 the BAS5 plugin in addition to the SOA-P plugin, is finding the SOA-P server

Bug 779085 (SOA-1484) - In JON 2.3 the BAS5 plugin in addition to the SOA-P plugin, is finding the SOA-P server

Summary: In JON 2.3 the BAS5 plugin in addition to the SOA-P plugin, is finding the SO...

Keywords:
Status:	CLOSED NEXTRELEASE
Alias:	SOA-1484
Product:	JBoss Enterprise SOA Platform 4
Classification:	JBoss
Component:	JON
Sub Component:
Version:	4.3 CP02
Hardware:	Unspecified
OS:	Unspecified
Priority:	high
Severity:	high
Target Milestone:	---
Target Release:	4.3 CP02
Assignee:	Jaroslaw Kijanowski
QA Contact:
Docs Contact:
URL:	http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2009-09-09 03:25 UTC by Len DiMaggio
Modified:	2009-09-30 00:35 UTC (History)
CC List:	1 user (show)
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Clone Of:
Environment:	SOA-P 4.3 CP02 CR3 jon-server-2.3.0-8299.zip
Last Closed:	2009-09-30 00:35:44 UTC
Type:	Bug

Attachments	(Terms of Use)
Screenshot.png (182.31 KB, image/png) 2009-09-23 17:13 UTC, Len DiMaggio	no flags	Details
View All Add an attachment (proposed patch, testcase, etc.)

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Red Hat Issue Tracker	SOA-1484	0	None	None	None	Never

Description Len DiMaggio 2009-09-09 03:25:48 UTC

Complexity: Low
Date of First Response: 2009-09-09 11:52:11
project_key: SOA

In JON 2.3 (jon-server-2.3.0-8299.zip), the JBAS5 plugin (jopr-jboss-as-5-plugin-2.3.0-SNAPSHOT.jar, from the jon-plugin-pack-eap-2.3.0-SNAPSHOT.zip), in addition to the JBAS4 plugin, is finding the SOA-P server.

--------------------------
dimaggi.csb JBossSOA 4.3.0.GA_CP02_SOA production (0.0.0.0:1099)         localhost.localdomain         JBossAS Server         JBossAS5         JBoss Enterprise SOA Platform
--------------------------

Comment 1 Len DiMaggio 2009-09-09 03:30:50 UTC

Link: Added: This issue is a dependency of JBNADM-3682

Comment 2 Ian Springer 2009-09-09 15:14:34 UTC

Complexity: Added: Low

Comment 3 Ian Springer 2009-09-09 15:43:06 UTC

Link: Added: This issue depends JOPR-374

Comment 4 Ian Springer 2009-09-09 15:52:11 UTC

This was a bug in the Jopr AS5 plugin. It was not filtering out SOA-P 4.x servers as it should have been. Jopr r1175 fixes the issue.

Comment 5 Len DiMaggio 2009-09-10 15:09:08 UTC

Hi Len,

This should be fixed now. If you want to test it out, you can grab an
updated copy of the AS5 plugin from here:

https://snapshots.jboss.org/maven2//org/jboss/on/jopr-jboss-as-5-plugin/2.3.0-SNAPSHOT/jopr-jboss-as-5-plugin-2.3.0-20090909.161534-105.jar

To verify, copy the updated plugin jar into your JON Server's
rhq-plugins dir, wait for the Server log to say the plugin was updated,
run the "plugins update" command from the Agent prompt, then run the
"discovery" Agent prompt command and inspect the output for the
"JBossAS5 plugin.JBossAS Server" Resource type, e.g.:

JBossAS5.JBossAS Server: Starting discovery...
JBossAS5.JBossAS Server: Process scan detected a server -
scan=[ProcessScan:
query=[process|basename|match=^java.*,arg|org.jboss.Main|match=.*],
name=[jbossas]]
, process=[process: pid=[5616], name=[C:\opt\jdk-1.6.0_16\bin\java.exe],
ppid=[5356]]
JBossAS5.JBossAS Server: Process scan detected a server -
scan=[ProcessScan:
query=[process|basename|match=^java.*,arg|org.jboss.Main|match=.*],
name=[jbossas]]
, process=[process: pid=[6724], name=[C:\opt\jdk-1.6.0_16\bin\java.exe],
ppid=[7516]]
JBossAS5.JBossAS Server: Process scan detected a server -
scan=[ProcessScan:
query=[process|basename|match=^java.*,arg|org.jboss.Main|match=.*],
name=[jbossas]]
, process=[process: pid=[7972], name=[C:\opt\jdk-1.6.0_16\bin\java.exe],
ppid=[7832]]
JBossAS5.JBossAS Server:
key=[C:\opt\jboss-eap-5.0.0-SNAPSHOT\server\default], name=[MAINFRAME
JBoss EAP 5.0.3.Branch default (127.0.0.50:1099)], version=[5.0.3
.Branch], description=[JBoss Enterprise Application Platform]
JBossAS5.JBossAS Server: Done.

As in the above example, it should *not* contain a "JBossAS5.JBossAS
Server: key=..." line for any SOA-P 4.x servers.

The check the output for the "JBossAS.JBossAS Server" Resource type and
verify that it does include a "key=..." line for all SOA-P 4.x servers.

Regards,
Ian

Comment 6 Len DiMaggio 2009-09-10 15:10:08 UTC

Still a problem...

> discovery
Apache.Apache HTTP Server: Starting discovery...
Apache.Apache HTTP Server: Done.

JBossAS.JBossAS Server: Starting discovery...
JBossAS.JBossAS Server: Process scan detected a server - scan=[ProcessScan: query=[process|basename|match=^java.*,arg|org.jboss.Main|match=.*], name=[JBoss4]], process=[process: pid=[28479], name=[/usr/lib/jvm/java-1.5.0-sun-1.5.0.18.x86_64/bin/java], ppid=[28470]]
JBossAS.JBossAS Server: Process scan detected a server - scan=[ProcessScan: query=[process|basename|match=^java.*,arg|org.jboss.Main|match=.*], name=[JBoss4]], process=[process: pid=[28066], name=[/usr/lib/jvm/java-1.5.0-sun-1.5.0.18.x86_64/bin/java], ppid=[28031]]
JBossAS.JBossAS Server: key=[/opt/JON_230/jon-server-2.3.0-SNAPSHOT/jbossas/server/default], name=[stacks5.lab.bos.redhat.com Jopr Server,  JBossAS 4.2.3.GA default (0.0.0.0:2099)], version=[4.2.3.GA], description=[JBoss Application Server hosting the Jopr Server]
JBossAS.JBossAS Server: key=[/opt/43_CP02_CR3/jboss-soa-p.4.3.0/jboss-as/server/production], name=[stacks5.lab.bos.redhat.com JBossSOA 4.3.0.GA_CP02_SOA production (0.0.0.0:1099)], version=[4.3.0.GA_CP02_SOA], description=[JBoss Enterprise SOA Platform]
JBossAS.JBossAS Server: Done.

JBossAS5.JBossAS Server: Starting discovery...
JBossAS5.JBossAS Server: Process scan detected a server - scan=[ProcessScan: query=[process|basename|match=^java.*,arg|org.jboss.Main|match=.*], name=[jbossas]], process=[process: pid=[28479], name=[/usr/lib/jvm/java-1.5.0-sun-1.5.0.18.x86_64/bin/java], ppid=[28470]]
JBossAS5.JBossAS Server: Process scan detected a server - scan=[ProcessScan: query=[process|basename|match=^java.*,arg|org.jboss.Main|match=.*], name=[jbossas]], process=[process: pid=[28066], name=[/usr/lib/jvm/java-1.5.0-sun-1.5.0.18.x86_64/bin/java], ppid=[28031]]
JBossAS5.JBossAS Server: Done.

JMX.JMX Server: Starting discovery...
JMX.JMX Server: Done.

RHQAgent.RHQ Agent: Starting discovery...
RHQAgent.RHQ Agent: key=[stacks5 RHQ Agent], name=[stacks5 RHQ Agent], version=[1.3.0-SNAPSHOT], description=[RHQ Management Agent]
RHQAgent.RHQ Agent: Done.

Postgres.Postgres Server: Starting discovery...
Postgres.Postgres Server: Done.

IIS.IIS: Starting discovery...
IIS.IIS: Done.

Comment 7 Ian Springer 2009-09-10 15:41:46 UTC

Actually, that output looks correct. Notice in the "JBossAS5.JBossAS Server" section, there are no "key=..." lines. This means no Resources were "JBossAS5.JBossAS Server" Resources were actually discovered. The process scan found a couple org.jboss.Main java processes, but then they were filtered out by the discovery code because they were version 4.x, not 5.x.

Comment 9 Ian Springer 2009-09-10 15:57:24 UTC

In the past, the SOA-P plugin pack has been a superset of the EAP plugin pack - it contained all of the plugins from EAP pack, as well as the ESB plugin. Do we want it to remain that way? If so, we'd need to add the jboss-as-5 and jboss-cache-v3 plugins to the SOA-P pack, which would add support for EAP 5.0.

Comment 10 Charles Crouch 2009-09-10 16:03:11 UTC

The SOA-P plugin pack should be made up of the latest EAP plugin pack + the ESB plugin. 

For testing the latest  EAP plugin pack is included in build QA-8229 from here: http://jon01.qa.atl2.redhat.com:8080/display/DEV/JON+QA+Release+History

We'll be releasing a CR2 shortly and then our GA, planned to be next week.

Comment 11 Len DiMaggio 2009-09-10 17:53:22 UTC

So, the SOA-P plugin pack will be a superset of the EAP plugin pack? This is different from the SOA-P plugin pack here: 

           http://jon01.qa.atl2.redhat.com:8042/dist/qa/plugin-packs-2.3.zip

Comment 13 Ian Springer 2009-09-10 21:39:27 UTC

That decision's for you guys (or perhaps someone in marketing/product management) to make. I just wanted to point out that you might want to consider including the additional plugins that the EAP pack includes.

Fyi, here's what the 3 additional plugins are used for:

jopr-jboss-as-5-plugin-2.3.0-SNAPSHOT.jar  - manage EAP 5.0 instances
jopr-jboss-cache-plugin-2.3.0-SNAPSHOT.jar - manage JBossCache v1/v2 (which is what ships w/ AS/EAP 4.x)
jopr-jboss-cache-v3-plugin-2.3.0-SNAPSHOT.jar - manage JBossCache v3 (which is what ships w/ AS/EAP 5.x)

Comment 16 Greg Hinkle 2009-09-15 14:35:59 UTC

JON automatically upgrades the datastore between versions. No data in the database should be lost if you follow the upgrade steps. (You utilize the same web installer and it just notices that there is an existing schema and asks the user if they would like to upgrade or replace. A backup is recommended.)

Comment 17 Ian Springer 2009-09-15 14:37:02 UTC

All data should be carried over, as long as the user chooses to upgrade, rather than overwrite, the existing DB, during the JON 2.3 installation. Detailed instructions on how to upgrade can be found in the JON install guide (staging version of the JON 2.3 install guide is here: http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Operations_Network/2.3/html/Installation_Guide/).

Comment 18 Jaroslaw Kijanowski 2009-09-15 14:44:17 UTC

What about the esb plugin update? Doesn't have the user to re-inventor the SOA-P when updating the esb plugin? This means that all historic data is lost, right?

Comment 19 Ian Springer 2009-09-15 14:51:43 UTC

Existing inventory should carry over after an upgrade too. The only way you would see issues is if you made changes to the Resource type names in the plugin or the Resource type hierarchy (e.g. renaming the ESB Server type to JBoss ESB Server, or moving the ESB Connector type under a different parent Resource type).

Comment 20 Dana Mison 2009-09-16 04:58:46 UTC

ok,

so...

rhq-jbossesb-plugin-SOA.4.3.0.GA_CP02.jar for JON 2.1.2

jon-plugin-pack-soa-2.3.0.zip for JON 2.3

I'm guessing rhq-jbossesb-plugin-SOA.4.3.0.GA_CP02.jar will be on the same CSP page as the SOA 4.3.CP02 download (as before)

what about the jon-plugin-pack-soa-2.3.0.zip download ?  the same ?

Comment 21 Dana Mison 2009-09-16 05:49:19 UTC

probably more to the point I need to know what the filenames for the zips will be for these on the CSP ?

Comment 22 Charles Crouch 2009-09-16 20:08:01 UTC

The SOA-P plugin pack that will get released with SOA-4.3CP02 and will have been certified on JON2.3 will be called

jon-plugin-pack-soa-2.3.0.GA.zip

The raw plugin for SOA-4.3CP02 I expect will be called

rhq-jbossesb-soa-plugin-SOA.4.3.0.GA_CP02.jar

but the ESB team will be building that so you should check with them for final word

WRT to location on the CSP. I'm not aware of any complaints around the current locations of these files, so they should go where the current SOA-P plugin packs and plugins live. You may want to check with Burr if he has any concerns over the present location.

Comment 23 Len DiMaggio 2009-09-17 03:02:49 UTC

Is this:

https://jira.jboss.org/jira/browse/SOA-1484?focusedCommentId=12485261#action_12485261

Still the latest soa plugin pack?  Is there a new pack that includes the ESB plugin?

Comment 24 Charles Crouch 2009-09-18 21:49:21 UTC

https://jira.jboss.org/jira/browse/SOA-1484?focusedCommentId=12485261#action_12485261  does not contain the latest ESB plugin

Comment 29 Ian Springer 2009-09-22 15:25:35 UTC

The v2.3 SOA plugin pack is now available at:

  http://jon01.qa.atl2.redhat.com:8042/dist/release/jon/2.3.0.GA/jon-plugin-pack-soa-2.3.0.GA.zip

Comment 30 Len DiMaggio 2009-09-23 00:58:56 UTC

jopr-jboss-as-5-plugin-2.3.0.GA.jar - javax.xml.bind.UnmarshalException [org.xml.sax.SAXParseException: cvc-complex-type.3.2.2: Attribute 'classLoader' is not allowed to appear in element 'server'

Using this SOA plugin pack with SOA-P 4.2 CP02: http://jon01.qa.atl2.redhat.com:8042/dist/release/jon/2.3.0.GA/jon-plugin-pack-soa-2.3.0.GA.zip

Results in this error:

jopr-jboss-as-5-plugin-2.3.0.GA.jar - javax.xml.bind.UnmarshalException [org.xml.sax.SAXParseException: cvc-complex-type.3.2.2: Attribute 'classLoader' is not allowed to appear in element 'server'

See log fragment below:

20:03:04,092 ERROR [MainDeployer] Could not start deployment: file:/jboss/local/43_CP02_CR4/jon/server/jon-server-2.1.0.GA/jbossas/server/default/deploy/rhq.ear/rhq-downloads/rhq-plugins/jopr-jboss-as-5-plugin-2.3.0.GA.jar
org.jboss.deployment.DeploymentException: Failed to parse plugin descriptor for plugin jar '/jboss/local/43_CP02_CR4/jon/server/jon-server-2.1.0.GA/jbossas/server/default/deploy/rhq.ear/rhq-downloads/rhq-plugins/jopr-jboss-as-5-plugin-2.3.0.GA.jar'.; - nested throwable: (javax.xml.bind.UnmarshalException
 - with linked exception:
[org.xml.sax.SAXParseException: cvc-complex-type.3.2.2: Attribute 'classLoader' is not allowed to appear in element 'server'.])
        at org.rhq.enterprise.server.core.plugin.ProductPluginDeployer.preprocessPlugin(ProductPluginDeployer.java:564)
        at org.rhq.enterprise.server.core.plugin.ProductPluginDeployer.start(ProductPluginDeployer.java:514)
        at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
        at sun.reflect.GeneratedMethodAccessor42.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
        at $Proxy50.deploy(Unknown Source)
        at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
        at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
        at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
        at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
        at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
        at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
        at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
        at $Proxy0.start(Unknown Source)
        at org.jboss.system.ServiceController.start(ServiceController.java:417)
        at org.jboss.system.ServiceController.start(ServiceController.java:435)
        at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
        at $Proxy4.start(Unknown Source)
        at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
        at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
        at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015)
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
        at sun.reflect.GeneratedMethodAccessor42.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
        at $Proxy9.deploy(Unknown Source)
        at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
        at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
        at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
        at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
        at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
        at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
        at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
        at $Proxy0.start(Unknown Source)
        at org.jboss.system.ServiceController.start(ServiceController.java:417)
        at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
        at $Proxy4.start(Unknown Source)
        at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
        at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
        at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
        at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
        at $Proxy5.deploy(Unknown Source)
        at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
        at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
        at org.jboss.Main.boot(Main.java:200)
        at org.jboss.Main$1.run(Main.java:508)
        at java.lang.Thread.run(Thread.java:619)
Caused by: javax.xml.bind.UnmarshalException
 - with linked exception:
[org.xml.sax.SAXParseException: cvc-complex-type.3.2.2: Attribute 'classLoader' is not allowed to appear in element 'server'.]
        at javax.xml.bind.helpers.AbstractUnmarshallerImpl.createUnmarshalException(AbstractUnmarshallerImpl.java:315)
        at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.createUnmarshalException(UnmarshallerImpl.java:506)
        at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0(UnmarshallerImpl.java:215)
        at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:184)
        at javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal(AbstractUnmarshallerImpl.java:137)
        at javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal(AbstractUnmarshallerImpl.java:142)
        at javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal(AbstractUnmarshallerImpl.java:151)
        at org.rhq.enterprise.server.core.plugin.ProductPluginDeployer.getPluginDescriptor(ProductPluginDeployer.java:448)
        at org.rhq.enterprise.server.core.plugin.ProductPluginDeployer.preprocessPlugin(ProductPluginDeployer.java:562)
        ... 114 more
Caused by: org.xml.sax.SAXParseException: cvc-complex-type.3.2.2: Attribute 'classLoader' is not allowed to appear in element 'server'.
        at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)
        at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
        at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
        at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
        at org.apache.xerces.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(Unknown Source)
        at org.apache.xerces.impl.xs.XMLSchemaValidator.reportSchemaError(Unknown Source)
        at org.apache.xerces.impl.xs.XMLSchemaValidator.processAttributes(Unknown Source)
        at org.apache.xerces.impl.xs.XMLSchemaValidator.handleStartElement(Unknown Source)
        at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source)
        at org.apache.xerces.jaxp.validation.ValidatorHandlerImpl.startElement(Unknown Source)
        at com.sun.xml.bind.v2.runtime.unmarshaller.ValidatingUnmarshaller.startElement(ValidatingUnmarshaller.java:89)
        at com.sun.xml.bind.v2.runtime.unmarshaller.SAXConnector.startElement(SAXConnector.java:137)
        at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
        at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
        at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
        at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
        at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
        at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
        at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
        at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
        at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
        at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0(UnmarshallerImpl.java:211)
        ... 120 more

Comment 31 Ian Springer 2009-09-23 03:40:20 UTC

The SOA plugin pack v2.3 is only compatible with JON 2.3 or later. It looks like you tried to run it on JON 2.1.

Comment 32 Len DiMaggio 2009-09-23 16:45:26 UTC

That last comment was a user error - trying to run the 2.3 plugin with a 2.1 server - with a 2.3 server:

rhq-agent.latest.md5=aa06f1a9e292023fc20fd8426e5d6d86
rhq-agent.latest.version=1.3.0.GA
rhq-agent.latest.build-number=5192
12:35:58,744 INFO  [[/]] DownloadServlet: Starting the download servlet
12:35:58,748 INFO  [[/]] initializer: All business tier deployments are complete - finishing the startup
12:35:58,756 INFO  [SystemManagerBean] Confirmed that the installer has been undeployed
12:36:01,571 INFO  [ServerManagerBean] Removed 1 obsolete agent reference(s) to server localhost.localdomain
12:36:02,158 INFO  [[/]] initializer: Starting hibernate statistics monitoring
12:36:02,176 INFO  [[/]] initializer: Starting the agent-plugin deployer
12:36:02,260 INFO  [LicenseManager] [License owner=Len DiMaggio email=ldimaggio1 phone=NA expiration=never platforms=unlimited serverIPs=any plugins=all support=3]
12:36:05,767 INFO  [ProductPluginDeployer] Discovered agent plugin [Platforms]
12:36:05,887 INFO  [ProductPluginDeployer] Discovered agent plugin [RHQServer]
12:36:06,081 INFO  [ProductPluginDeployer] Discovered agent plugin [JBossAS5]
12:36:06,193 INFO  [ProductPluginDeployer] Discovered agent plugin [Hibernate]
12:36:06,288 INFO  [ProductPluginDeployer] Discovered agent plugin [JBossCache]
12:36:06,396 INFO  [ProductPluginDeployer] Discovered agent plugin [Postgres]
12:36:06,550 INFO  [ProductPluginDeployer] Discovered agent plugin [JBossAS]
12:36:06,647 INFO  [ProductPluginDeployer] Discovered agent plugin [IIS]
12:36:06,743 INFO  [ProductPluginDeployer] Discovered agent plugin [JBossESB]
12:36:06,866 INFO  [ProductPluginDeployer] Discovered agent plugin [Database]
12:36:07,082 INFO  [ProductPluginDeployer] Discovered agent plugin [Apache]
12:36:07,221 INFO  [ProductPluginDeployer] Discovered agent plugin [JBossCache3]
12:36:07,346 INFO  [ProductPluginDeployer] Discovered agent plugin [RHQAgent]
12:36:07,466 INFO  [ProductPluginDeployer] Discovered agent plugin [JMX]
12:36:11,830 INFO  [ProductPluginDeployer] Deploying [7] new or updated agent plugins: [JBossAS, JBossAS5, RHQServer, Hibernate, JBossCache3, JBossESB, JBossCache]

Comment 33 Len DiMaggio 2009-09-23 17:13:08 UTC

Resolved with:  http://jon01.qa.atl2.redhat.com:8042/dist/release/jon/2.3.0.GA/jon-plugin-pack-soa-2.3.0.GA.zip

Verified with 4.3 CP02 CR4 and this ^ soa plugin pack.

Comment 34 Len DiMaggio 2009-09-23 17:13:08 UTC

Attachment: Added: Screenshot.png

Comment 35 Len DiMaggio 2009-09-23 17:18:38 UTC

Resolved with:  http://jon01.qa.atl2.redhat.com:8042/dist/release/jon/2.3.0.GA/jon-plugin-pack-soa-2.3.0.GA.zip

Verified with 4.3 CP02 CR4 and this ^ soa plugin pack.

Comment 36 Len DiMaggio 2009-09-28 17:37:25 UTC

Reopening and marking as resolved - still needs to be verified by QE

The ESB plugin in ths .zip here:  http://jon01.qa.atl2.redhat.com:8042/dist/release/jon/2.3.0.GA/jon-plugin-pack-soa-2.3.0.GA.zip   is functionally correct but does not have the correct file name.

Comment 37 Len DiMaggio 2009-09-28 17:38:07 UTC

Assigning to Jarek to verify.

Comment 38 Jaroslaw Kijanowski 2009-09-29 06:46:08 UTC

Verified. The soa plugin pack contains exactly the same bits that have been tested. As you said, just the esb plugin needs to be renamed and we're ready to go.

293f3056cbe05544265f3a956e785683  jopr-hibernate-plugin-2.3.0.GA.jar
74433501fb868ff0bbea69838420f4db  jopr-jboss-as-5-plugin-2.3.0.GA.jar
05b38ab2de6957e3296e342e4b55d461  jopr-jboss-as-plugin-2.3.0.GA.jar
7883c8753e165556c83dc207f3517de2  jopr-jboss-cache-plugin-2.3.0.GA.jar
5443e95f68f8080952fb5aa53e3a874e  jopr-jboss-cache-v3-plugin-2.3.0.GA.jar
51c32f9c3a88fda9b79d343dcccaedc4  jopr-rhq-server-plugin-2.3.0.GA.jar
c51b2ac924ce9eb842e7a08980b61e69  rhq-jbossesb-soa-plugin-SOA.4.3.0.GA_CP02_CR4.jar

Comment 39 Len DiMaggio 2009-09-30 00:35:44 UTC

In zip file: 
    http://jon01.qa.atl2.redhat.com:8042/dist/release/jon/2.3.0.GA/jon-plugin-pack-soa-2.3.0.GA.zip

Here is the SOA ESB plugin:
   c51b2ac924ce9eb842e7a08980b61e69  rhq-jbossesb-soa-plugin-SOA.4.3.0.GA_CP02.jar

Note You need to log in before you can comment on or make changes to this bug.