Documentation for JIRA 6.3. Not using this? See below:
(JIRA 6.2.x documentation | JIRA Cloud documentation | earlier versions of JIRA)

Skip to end of metadata
Go to start of metadata

This page contains additional notes, tips, tricks and caveats on connecting JIRA to MySQL, which supplements the official MySQL installation documentation. Many of these notes are contributed by users, based on their specific experiences in connecting JIRA to MySQL.

  • No labels

7 Comments

  1. Greetings!

    I was trying to get the user details of my our JIRA users from the MySQL database.  Reading your documentation I found that the user-related table schemas in MySQL is different from those in HSQLDB. One example is the 'propertysets' table, it does not exist in MySQL.  While in MySQL there is 'userbase' (id, username, password_hash fields) and 'propertystring' (id, propertyvalue fields) I don't know how the username is linked/related to the 'propertystring' table.

    Am i missing something here?

    Thanks

  2. I was receiving the following error during JIRA start-up and JIRA was failing to start.

    2008-10-06 15:46:11,265 Thread-1 ERROR [ContainerBase.[Catalina].[localhost].[/]] Exception sending context initialized event to listener instance of class com.atlassian.jira.appconsistency.db.DatabaseCompatibilityEnforcer
    com.atlassian.jira.exception.DataAccessException: java.sql.SQLException: Can't create/write to file 'C:\WINDOWS\TEMP#sql_178c_0.MYI' (Errcode: 13)

    This error was followed by a long list database errors. Looking like the following.

    2008-10-06 15:46:15,015 Thread-1 [core.entity.jdbc.DatabaseUtil] Entity "Action" has 11 fields but table "jiraaction" has 0 columns.

    Problem was the MacAfee On-Access Virus Scan was enabled.  I disabled this and JIRA started without errors.

    I hope this can help somebody.

  3. Anonymous

    Just a quick note to anyone installing JIRA standalone on Vista (Home Premium, maybe others) machines, and attempting to change from HSQL to MySQL.

    Vista by default doesn't define 127.0.0.1 as localhost; either MySQL, Apache, or JIRA expects localhost communications to be on that IP when told to go to localhost. As such, you will end up with a Connection Refused (Socket) error while trying to start Jira up (as Vista would route to 0.0.0.0 instead -- gargh! -- and the system will then refuse to talk).

    The solution/ workaround is simply to add 127.0.0.1 as localhost into the host file. My Jira instance is now humming nicely along -- after some 4 ~ 5 hours of troubleshooting with entityengine.xml and server.xml. Thanks, MS.

    Here's a link to the page that finally twigged me to this little feature -- external link to mysql forums:

    http://forums.mysql.com/read.php?39,254732,258702#msg-258702

  4. Anonymous

    If you're on Centos 5 (and probably RHEL5) make sure you have naming-factory-dbcp.jar in your common/lib for some bizarre reason that jar is missing so your datasource resource doesn't get registered in JNDI

    1. Anonymous

      To which common/lib directory does this refer (i.e.: what is the full path) and where should I be able to find naming-factory-dbcp.jar?

  5. Anonymous

    Please note that if you get an error like NullPointerException in org.ofbiz.[...].SQLProcessor.getConnection(Oops page from Jira) when connecting it is because the plugin manager can not log into the database when the password has special characters.  To fix this (and not having to restart the install) change the JIRA DB user's password in the dbconfig.xml located in app-data's jira directory (/var/atlassian/application-data/jira in my case)

    1. Anonymous

      Sorry about the above... Please ignore the link it is not related