Bug 835687

Summary: Upgrade postgres driver to v9.1-902.jdbc4
Product: [Other] RHQ Project Reporter: krzykwas
Component: Core Server, Core UIAssignee: Charles Crouch <ccrouch>
Status: CLOSED CURRENTRELEASE QA Contact: Mike Foley <mfoley>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.4CC: ccrouch, hbrock, hrupp
Target Milestone: ---   
Target Release: RHQ 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 4.5 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-01 10:03:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description krzykwas 2012-06-26 20:24:36 UTC 
Description of problem:
   RHQ does not work with Postgres 9.1.4 in the default configuration. When trying to log on to the RHQ at http://127.0.0.1:7080, I got an error related to connecting to the database which finally boiled down to an exception: „column index out of range: 2, column count: 1”.
   When I upgraded the postgres driver from 
postgresql-9.1-901.jdbc4.jar to postgresql-9.1-902.jdbc4.jar, the problems were gone.

Version-Release number of selected component (if applicable):
   RHQ version: 4.5.0, though it probably affects also older versions.

Steps to Reproduce:
1. Start an RHQ server.
2. Try to log on with default credentials rhqadmin/rhqadmin.
3. The logging is unsuccessful and a stack trace appears in the log file.
  
Actual results:
You cannot log on.

Expected results:
You are logged on and can modify rhq settings.

Additional info:
Updating the driver seems to fix: https://bugzilla.redhat.com/show_bug.cgi?id=741855
Comment 1 Ian Springer 2012-06-26 20:36:33 UTC 
Done in master:

http://git.fedorahosted.org/git/?p=rhq/rhq.git;a=commitdiff;h=aa77d7e
Comment 3 Heiko W. Rupp 2013-09-01 10:03:06 UTC 
Bulk closing of items that are on_qa and in old RHQ releases, which are out for a long time and where the issue has not been re-opened since.