JIRA 4.3 : JIRA Cannot Create Issues when Using MySQL with Binary Logging
This page last changed on Feb 16, 2011 by ggaskell.
If you use JIRA with MySQL and attempt to create a JIRA issue, JIRA may generate an error similar to the following: Error creating issue: Could not create workflow instance: root cause: while inserting: [GenericEntity:OSWorkflowEntry][id,null][name,jira][state,0] (SQL Exception while executing the following:INSERT INTO OS_WFENTRY (ID, NAME, INITIALIZED, STATE) VALUES (?, ?, ?, ?) (Binary logging not possible. Message: Transaction level 'READ-COMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT')) OR Binary logging not possible. Message: Transaction level 'READ-COMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT' You may encounter this problem if your JIRA MySQL database configuration:
JIRA uses the 'READ-COMMITTED' transaction isolation level with MySQL, which currently only supports row-based binary logging. For more information about this, please refer to MySQL issue no. 40360. To overcome this problem, you must configure MySQL's binary logging format to use 'row-based' binary logging. To do this:
|
![]() |
Document generated by Confluence on Mar 27, 2011 18:52 |