Hide Forgot
Description of problem: I am unable to install EAP (or any) plugin to upgraded instance of JON-2.4.2. It seems like Version-Release number of selected component (if applicable): 2.4.1.GA ->version: 2.4.2.GA build number: 3fd0075:1afdc60 How reproducible: always Steps to Reproduce: 1. install JON 2.4.1.GA, install EWS plugin, EAP plugin, SOA plugin 2. run any agent (maybe not necessary) 3. upgrade 2.4.1 to 2.4.2 (server only) 4. install ONLY EAP plugin update (copy jars into /plugins and press 'Scan for updates' in UI Actual results: UI reports: Failed to scan for updated plugins Cause: java.lang.Exception:File [/data/rhq/upg241-242/jon-server-2.4.2.GA/jbossas/server/default/deploy/rhq.ear/rhq-downloads/rhq-plugins/jopr-tomcat-plugin-3.0.1.GA.jar] is not a valid jarfile - it is either corrupted or file has not been fully written yet. No other plugins are updated. Expected results: EAP plugins are updated Additional info: Original (the one installed into 2.4.1) jopr-tomcat-plugin-3.0.1.GA.jar is 101659 bytes long Invalid file present in rhq.ear reporting error is 213317 bytes long, this is +-1byte exactly double size. In fact, all plugins in 2.4.2 rhq.ear/rhq-downloads/rhq-plugins are doublesized.
Created attachment 551152 [details] 2.4.2 server log attached 2.4.2 server log. I forgot to mention I am running it on postgres 9.0.5
"In fact, all plugins in 2.4.2 rhq.ear/rhq-downloads/rhq-plugins are doublesized." Well I expect that is the problem, but I don't understand how a fresh install could work with these jumbo plugins. If this is the case, then it certainly sounds like a build issue.
All plugins, I mean plugins that have been copied over from 2.4.1 installation during upgrade. I have: jon-2.4.1 using db jon How did I upgrade? I create jon-2.4.2, start it ant let it use db jon. Upgrade process - new jon-2.4.2 looks to jon 2.4.1 and copies plugins, that are not present in jon-2.4.2 and we get jon-2.4.2 with 2.4.1 plugins. Then I need to install new versions of plugins. Is it how upgrade works, right? I've installed jon 2.4.2 with EWS and EAP plugins, and plugins size's are OK. So the only way how to doublesize was during upgrade/copying.
Not an issue on postgres 8.4
Release notes should be updated in a way, that we support only postgres 8.x not 9
This is already in the release notes for 2.4: http://docs.redhat.com/docs/en-US/JBoss_Operations_Network/2.4/html/Release_Notes/supported-platforms.html#server-databases and for 2.4.1: http://docs.redhat.com/docs/en-US/JBoss_Operations_Network/2.4/html/2.4.1_Release_Notes/index.html#server-databases At least, the 2.4.x release notes explicitly list the supported 8.x versions and don't list 9.x at all. The support matrix on the site needs to be updated: http://www.redhat.com/jboss_on/requirements/ That simply lists 8.2.4 and later, which isn't entirely accurate, I think. Re-assigning to Alan.
I'll update the website. However, due to upcoming changes to the website this won't happen until after 1/25/2012.
Wait - we just hijacked this BZ. I'm closing this entry, it's not a bug. If someone wanted to enter an RFE that JON ought to be a little more critical about what databases it appears to work with then I'll get behind it. I'll track the website update separately and the release notes are correct.