The ActiveObjects library appears to have incompatibilities with MySQL JDBC Connector 8.0.11. It's unable to detect existing AO_ tables (after upgrade) or create new AO_ tables (for new installations, encountered at least once during Bamboo reproduction attempts). Looks like it's targeting the wrong database / schema.
- Bamboo 6.5.0
- Bitbucket 5.10.0
- Fisheye/Crucible 4.5.3
- MySQL 5.7
- MySQL JDBC Connector 8.0.11
- Other products unconfirmed / tested.
- Create two MySQL databases (grant permissions to both databases for the same user)
- Install Bamboo 6.5.0
- Copy the MySQL JDBC Connector 8 into <bamboo-install>/lib
- Start Bamboo and install it using one of the databases from Step 1
- Immediately there should be errors referencing the AO_2F1435_HEALTH_CHECK_STATUS table in the logs.
- Create a plan and perform a build
- Click the build result -> Internal Server Error regarding AO_7A45FB_AOTRACKING_ENTRY
- If there isn't any errors, try restarting Bamboo. There does appear to be some level of inconsistency to reproduction.
- Install Bitbucket 5.10
- Copy the MySQL JDBC Connector 8 into <bitbucket-home>/lib
- Start Bitbucket and install it using a MySQL database
- Navigate to the Bitbucket URLs (errors should have already started due to background tasks)
- Install Fisheye/Crucible 4.5.3
- Copy the MySQL JDBC Connector 8 into <FISHEYE_INST>/lib
- Start Fisheye/Crucible and complete the setup wizard
- Migrate to MySQL
- In the administration area, try accessing the 'Smart Commits' menu option on the left
AO tables are found in the correct schema and created.
The below exception is thrown in the atlassian-bitbucket.log:
- Many other AO tables such as AO_777666_JIRA_INDEX, AO_D6A508_IMPORT_JOB and AO_92D5D5_REPO_NOTIFICATION will also present the same error without any action in the UI. Presumably background tasks.
The below exception is thrown in the atlassian-bamboo.log file:
Note, the schema bamboo1 is not the one defined in the JDBC connection string, it's another database:
If we then go and drop bamboo1 (empty db created for reproduction purposes), it starts looking in sys schemas such as information_schema instead:
The below exception is thrown in the atlassian-fisheye.log file after clicking on the 'Smart Commits' menu:
The atlassian-fisheye.log also report problems with the AO_2913F5_COMMENT_ISSUE Active Objects table:
Downgrade the JDBC connector to 5.1.46 and restart the application: