[#5588] - Upgrade from 4.1.0 to 4.2.1 fails due to validation error

Category:
Bug report
Priority:
Normal
Status:
New
Project: Severity:
Major
Resolution:
Open
Component: Reproducibility:
Always
Assigned to:

I'm on Debian 6.0 Squeeze Tomcat6 (6.0.28). I had an issue when upgrading. I don't have any foodmart or sugarcrm installed but the validation is testing for these installations anyway.

Error:
[advanced-sql] 1 of 1 SQL statements executed successfully
[echo] Connection OK
[echo] Validating FoodMart database connection at jdbc:mysql://localhost:3306/foodmart?useUnicode=true&characterEncoding=UTF-8&autoReconnect=true&autoReconnectForPools=true. Phase: [test]
[echo] About to validate JDBC jar existence
[echo] Look in: /usr/src/jasperserver/jasperreports-server-cp-4.2.1-bin/buildomatic/conf_source/db/mysql/jdbc
[echo] Found jar file: assuming OK
[advanced-sql] Failed to connect: Unknown database 'foodmart'
[echo] Connection failed:
[echo] SQLState: 42000
[echo] Vendor specific error code: 1049
[echo] Message: [Unknown database 'foodmart']

BUILD FAILED
/usr/src/jasperserver/jasperreports-server-cp-4.2.1-bin/buildomatic/bin/validation.xml:494: The following error occurred while executing this line:
/usr/src/jasperserver/jasperreports-server-cp-4.2.1-bin/buildomatic/bin/validation.xml:370: The following error occurred while executing this line:
/usr/src/jasperserver/jasperreports-server-cp-4.2.1-bin/buildomatic/conf_source/db/mysql/db.xml:58: The following error occurred while executing this line:
/usr/src/jasperserver/jasperreports-server-cp-4.2.1-bin/buildomatic/bin/validation.xml:424: The following error occurred while executing this line:
/usr/src/jasperserver/jasperreports-server-cp-4.2.1-bin/buildomatic/bin/validation.xml:464: Database doesn't exist. Treating problem with JDBC connection as unrecoverable

I have solved this issue by commenting out line 494 and 495 in buildomatic/bin/validation.xml

E.g.:
<!-- <validateDB systemName="foodmart" phase="test" />
<validateDB systemName="sugarcrm" phase="test" /> -->

I suggest to put this into the documentation.

smirta's picture
1
Joined: Dec 23 2011 - 2:10am
Last seen: 11 years 1 month ago
Feedback