MySQL Binary Logging Problem with InnoDB When Creating a Workflow

お困りですか?

アトラシアン コミュニティをご利用ください。

コミュニティに質問

症状

When creating a Workflow, the user receives exceptions like:

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'))

Another possible scenario:

com.atlassian.jira.plugin.ext.bamboo.service.PlanStatusUpdateServiceImpl:job [module.propertyset.ofbiz.OFBizPropertySet] Error setting value in PropertySet
org.ofbiz.core.entity.GenericEntityException: while updating: [GenericEntity:OSPropertyString][id,11709][value,true] (SQL Exception while executing the following:UPDATE propertystring SET propertyvalue=? WHERE ID=? (Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging. InnoDB is limited to row-logging when transaction isolation level is READ COMMITTED or READ UNCOMMITTED.))

原因

This is required by MySQL:

Statement based binlogging does not work in isolation level
READ UNCOMMITTED and READ COMMITTED since the necessary
locks cannot be taken.

ソリューション

To change to row based binary logging, set the following in /etc/my.cnf (or your my.cnf if it's elsewhere):

binlog_format=row

Please see http://dev.mysql.com/doc/refman/5.1/en/binary-log-setting.html for more information.

Last modified on Mar 30, 2016

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する
Powered by Confluence and Scroll Viewport.