Hide Forgot
project_key: SOA Background: https://bugzilla.redhat.com/show_bug.cgi?id=682116 The issue is that, MEAD unpacks the plugin jars and signs them; when it puts them back together it does so in a different order The problem is resolved in RHQ 3.0.1 The problem is seen with SPA-P 5.2 ER1 as the admin console fails to load rhq-jmx-plugin.jar and jopr-jboss-cache-v3-plugin.jar
The problem may be resolved if we change all of the rhq*.jar and jopr*.jar in the admin console - moving from version 3.0.0 to 3.0.1
Attached server.log - the error seen is: 2011-07-20 11:24:07,465 ERROR [org.rhq.core.pc.plugin.PluginManager] (http-127.0.0.1-8080-1) Plugin [JMX] at [file:/jboss/local/52_ER1/jboss-soa-p-5/jboss-as/server/default/deploy/admin-console.war /plugins/rhq-jmx-plugin.jar] could not be loaded and will therefore not be deployed. org.rhq.core.clientapi.descriptor.PluginTransformException: No version is defined for plugin jar [file:/jboss/local/52_ER1/jboss-soa-p-5/jboss-as/server/default/deploy/admin-console.war/plugins/rhq -jmx-plugin.jar]. A version must be defined either via the MANIFEST.MF 'Implementation-Version' attribute or via the plugin descriptor 'version' attribute.
Attachment: Added: server.log
Question - how is the console built? Are RHQ bits replaced in the productization process? There is a JON patch (to 2.4.1) that fixes this.
The console is part of EAP; we only tweak the config files. We could apply the JON patch during the SOA-P build.
Charles Crouch <ccrouch> made a private comment on [bug 682116|https://bugzilla.redhat.com/show_bug.cgi?id=682116]
Link: Added: This issue relates to SOA-3230
Mike Bonnet has fixed MEAD
Release Notes Docs Status: Added: Not Required Writer: Added: dlesage
Verified fixed in ER3 build.