Hide Forgot
project_key: SOA Starting server default and opening admin console results in the following error in server's stdout: 14:59:49,017 INFO [BootstrapAction] Initializing Administration Console v1.3.4.SP1... 14:59:52,480 ERROR [PluginManager] Plugin [Platforms] at [jndi:/localhost/admin-console/plugins/rhq-platform-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 [jndi:/localhost/admin-console/plugins/rhq-platform-plugin.jar]. A version must be defined either via the MANIFEST.MF 'Implementation-Version' attribute or via the plugin descriptor 'version' attribute.
Investigate for SOA 5.1.0
Just tried this on ER4 and could not reproduce the issue, can you try again and upload your logs? I see the following output 15:12:05,096 INFO [BootstrapAction] Initializing Administration Console v1.3.4.SP1... 15:12:10,621 INFO [PluginContainerResourceManager] Discovering Resources... The plugin does not appear to have changed since ER3.
please find server log at http://hudson.qa.jboss.com/hudson/view/SOA-Release/job/soa-eds-plugins-and-adminshell/94/artifact/jbosssoa/jboss-as/server/default/log/server.log
Please let me investigate a little bit more. Will update you later.
The issue is the plugin jar files included in that server, however I don't know where they come from. They do not match the version in the released zips and are not of the right format. Are these being processed in any way? The versions I know about are http://jawa05.englab.brq.redhat.com/candidate/SOA-5.1-ER4/signed/soa-5.1.0.ER4.zip http://jawa05.englab.brq.redhat.com/candidate/SOA-5.1-ER4/unsigned/soa-5.1.0.ER4.zip sha1sums for one of the plugins de5a50e5765750ea13e26a7cde79bf5ad3866649 jboss-soa-p-5/jboss-as/server/default/deploy/admin-console.war/plugins/rhq-platform-plugin.jar 50d3ecfbce50a96f4d5ac6bb997f3a6c68891fcc unsigned/jboss-soa-p-5/jboss-as/server/default/deploy/admin-console.war/plugins/rhq-platform-plugin.jar
The issue may be the QE tool that strips out the signed information from the jar files, as it may not repackage the jar correctly. The jar file structure assumes that the manifest is the first file in the archive or is only preceded by the META-INF directory entry, as such the plugins in the QE build are invalid. The rhq-platform-plugin.jar contains the following entries META-INF/ META-INF/maven/ META-INF/maven/org.rhq/ META-INF/maven/org.rhq/rhq-platform-plugin/ org/ org/rhq/ org/rhq/plugins/ org/rhq/plugins/platform/ org/rhq/plugins/platform/content/ org/rhq/plugins/platform/content/yum/ org/rhq/plugins/platform/win/ META-INF/MANIFEST.MF ..... Whereas the correct structure should start with the manifest, such as the following from one of the original rhq-platform-plugin.jar files META-INF/MANIFEST.MF META-INF/JBOSSCOD.SF META-INF/JBOSSCOD.RSA META-INF/ META-INF/rhq-plugin.xml
java -jar manifest.jar <filenames> to test
Attachment: Added: manifest.jar
Yes, this seems to be my fault. I'll fix the tool tomorrow.
The tool has been fixed. For the changes to take effect, soa-5.1 job must be rerun. I suggest to postpone that for the next ER if there is no urgent need. The tool can ale be used locally on a workstation.
Cool, thanks. No need to rebuild. I just saw the message and reported it. It doesn't get in my way.
No need to include this one in release notes. It was a problem with a test build.
Writer: Added: dlesage
Verified during testing of ER9.
Temporarily reopening to update release note info.
Release Notes Docs Status: Added: Documented as Resolved Issue Release Notes Text: Added: https://issues.jboss.org/browse/SOA-2466 An error would appear in the stdout if the Administration Console was run under the default deployment. The message stated that the "Plugin [Platyform] at [jndi:/localhost/admin-console/plugins/rhq-platform-plugin.jar] could not be loaded and will therefore not be deployed." This was caused by the plug-in tool stripping out data. The tool has been changed and, as a result, the user will no longer see this error.
Release Notes Text: Removed: https://issues.jboss.org/browse/SOA-2466 An error would appear in the stdout if the Administration Console was run under the default deployment. The message stated that the "Plugin [Platyform] at [jndi:/localhost/admin-console/plugins/rhq-platform-plugin.jar] could not be loaded and will therefore not be deployed." This was caused by the plug-in tool stripping out data. The tool has been changed and, as a result, the user will no longer see this error. Added: https://issues.jboss.org/browse/SOA-2466 An error would appear in the stdout if the Administration Console was run under the default deployment. The message stated that the "Plugin [Platyform] at [jndi:/localhost/admin-console/plugins/rhq-platform-plugin.jar] could not be loaded and will therefore not be deployed." This was caused by a QE tool stripped out the signing information from JAR files. The tool has been changed and, as a result, the user will no longer see this error.
Reopening to modify release note text; will set back to Closed -> Done momentarily.
Setting to Closed -> Done, having modified the release notes text.
Release Notes Text: Removed: https://issues.jboss.org/browse/SOA-2466 An error would appear in the stdout if the Administration Console was run under the default deployment. The message stated that the "Plugin [Platyform] at [jndi:/localhost/admin-console/plugins/rhq-platform-plugin.jar] could not be loaded and will therefore not be deployed." This was caused by a QE tool stripped out the signing information from JAR files. The tool has been changed and, as a result, the user will no longer see this error. Added: https://issues.jboss.org/browse/SOA-2466 An error appeared in stdout if the Administration Console was run under the default deployment. The message stated that the "Plugin [Platyform] at [jndi:/localhost/admin-console/plugins/rhq-platform-plugin.jar] could not be loaded and will therefore not be deployed." This occurred because the JAR file did not contain signing information. The JAR file has been modified appropriately, and the error no longer appears in the log.