Browser gives error 500 Edited

I'm getting an error when I attempt to access a sample project. This is a new installation. It looks like the error is from mysql, can someone offer directions on how to fix this. The instructions I'm following worked on an AWS Amazon Centos install but having trouble on my local machine running Centos 7.2.3.


com.atlassian.activeobjects.internal.ActiveObjectsInitException: bundle [com.atlassian.plugins.base-hipchat-integration-plugin-api]
com.atlassian.activeobjects.internal.ActiveObjectsInitException: bundle [com.atlassian.plugins.base-hipchat-integration-plugin-api]
	at com.atlassian.activeobjects.osgi.TenantAwareActiveObjects$1$1$ [?:?]
	at com.atlassian.activeobjects.osgi.TenantAwareActiveObjects$1$1$ [?:?]
	at [?:?]
	at [?:1.8.0_102]
	at java.util.concurrent.ThreadPoolExecutor.runWorker( [?:1.8.0_102]
	at java.util.concurrent.ThreadPoolExecutor$ [?:1.8.0_102]
	at [?:1.8.0_102]
Caused by: com.atlassian.activeobjects.internal.ActiveObjectsSqlException: There was a SQL exception thrown by the Active Objects library:
    	- name:MySQL
    	- version:5.7.19
    	- minor version:7
    	- major version:5
    	- name:MySQL Connector Java
    	- version:mysql-connector-java-5.1.34 ( Revision: )
    com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: REFERENCES command denied to user 'jirauser'@'localhost' for table 'AO_5FB9D7_AOHIP_CHAT_LINK'
	at com.atlassian.activeobjects.internal.EntityManagedActiveObjects.migrate( [?:?]

1 answer

Hi Chris,

This error is covered in com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: REFERENCES command denied to user:

The cause for this is explained deeper in MySQL :: MySQL 5.7 Reference Manual :: 7.2.1 Privileges Provided by MySQL

The REFERENCES privilege is unused before MySQL 5.7.6. As of 5.7.6, creation of a foreign key constraint requires the REFERENCES privilege for the parent table.

Since this was unused, our previous documentation/guides never made note that this was required.  Since MySQL has changed its requirements, in turn Atlassian has also updated our documentation on how MySQL databases must be configured in order to work properly with JIRA.

Hence this error can happen anytime the database user has not be granted the needed permissions, and JIRA is expected to create a new foreign key constraint.

The documentation on Connecting JIRA 7.3 applications to MySQL now has the correct SQL commands need to configure the user permissions correctly.   The new command is:

flush privileges; 



Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Posted yesterday in Jira

We want to know what Jira Service Desk apps you're using!

Hi Community! My name is Amir and I’m on the Jira Service Desk product marketing team at Atlassian. Our team would love to understand how you’re leveraging our ecosystem for Jira Service Desk. Wha...

40 views 0 5
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you