Description of problem: Clicking on the link Bundles->Repositories->JBoss Patches displays a globally uncaught exception in UI and message center. Please find attached the details of error in message center and the screenshot. There are no errors in server or agent log. Version-Release number of selected component (if applicable): Build: Version: 3.1.1.ER2 Build Number: f546515:4eb3f2c Database: PostgreSQL 8.3.8 Browser: Firefox 10.0.2 Java Version: jre1.7.0_05 How reproducible: Always Steps to Reproduce: 1. Login to imanage UI. 2. Navigate to Bundles menu. 3. In the left pane, expand the 'Repositories' section. 4. Click on the link JBoss Patches. Actual results: UI displays globally uncaught exception. Expected results: No error should be displayed Additional info: Also reproduced on jdk1.6.0_18.
Created attachment 604924 [details] Screenshot
Created attachment 604925 [details] Error_details
i see this too. Probably this is the repository that is created by the JBoss CSP server plugin. FYI: This isn't a 3.1.1. blocker. No one needs to use or even look at that repository tree to get things done (AFAIK). I think it was put in there because at one point there was some idea to use it to navigate and populate the repository from there. Nothing like that was ever done.
Assigning to Lukas Where did this repo come from? Was this also in jon300, jon310, I don't recall it being there?
This is present in both jon300 and jon310 out of the box.
As Mazz said, this is a repo automatically created by the CSP content source to pull the patches to.
As per 8/20 triage pushing to JON312
Per triage with loleary, crouch, mfoley: Move to JBoss ON product, set target release JON 3.2, clear priority (will be subject to further triage in JON 3.2 timeframe).
Looks like this was fixed upstream as per https://bugzilla.redhat.com/show_bug.cgi?id=851239#c1
moving to modified as the upstream fix should already be in the JON builds.
Moving to ON_QA for testing in the next build.
Verified on Version: 3.2.0.ER4 Build Number: e413566:057b211 The Repository section is not visible on the bundles screen.