Currently, the installer will test the database connection by simply making sure it can connect to it. We should also have it verify that the version of the database it is connecting to is supported. If it is not supported, the test-connection should fail. This will prohibit people from being able to install on an unsupported database (which will cause errors later on during runtime - see RHQ-1389 as an example).
When you click the Test Connection button or when you press Install! button, we not only check that we can connect to the database but we also check the version/vendor of the database and make sure it is not an unsupported version.
I installed JON with unsuported version of postgres DB. I pressed both the Test Connection and Install! button. The installation did not fail but finished with success. RHEL5.2, x86_64, PostgreSQL 8.1.11, JON RHQ SVN rev# 2733
can you give me all the log files that were produced (in the <install>/logs) directory -just zip them up and attach the zip file.
Zipped <INSTALL_DIR>/logs/*.* files.
I added requested <INSTALL_DIR>/logs/*.* files.
found the problem - it was a very subtle yet potentially nasty bug with an internal cache inside db factory. this is fixed. also had to fix some version checking code in the db factory. svn rev 2807
I retested the installation process with supported/unsupported instances of postgres/oracle databases. It worked as expected. RHEL5.3, x86_64, Unsupported: Oracle9i EE/PostgreSQL 8.1.11, Supported: Oracle 10g XE/PostgreSQL8.2.4, JON RHQ SVN rev# 2894
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-1390 Imported an attachment (id=368532)