【问题标题】:JDBCResourceDAO Failed to delete the resource with id - WSO2 API ManagerJDBCResourceDAO 无法删除具有 id 的资源 - WSO2 API Manager
【发布时间】:2015-03-19 09:42:41
【问题描述】:

我将 WSO2 API Manager 1.8 与 MySQL 一起使用。我无缘无故地低于错误。

ERROR - JDBCResourceDAO Failed to delete the resource with id 758. 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.

java.sql.SQLException: 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 UN
COMMITTED.

我该如何解决这个问题?

【问题讨论】:

    标签: java mysql wso2 wso2carbon wso2-am


    【解决方案1】:

    由于使用 WSO2 产品在 Mysql DB 上进行复制而发生上述错误。

    根据ERROR 1598 (HY000): Binary Logging not Possible. Message: Transaction Level READ-COMMITTED in InnoDB is not Safe for Binlog Mode STATEMENT

    这个问题有几种解决方案:

    • 您需要将 binlog 模式更改为 ROWMIXED 以便将数据加载到数据库中

      mysql> SET GLOBAL binlog_format = 'ROW';
      
    • 如果您不打算使用 MySQL 服务器进行复制,请考虑通过删除 来自 mysqld 实用程序的命令选项的选项 --log-bin 启动 MySQL 服务器。

    【讨论】:

      猜你喜欢
      • 2021-08-07
      • 1970-01-01
      • 1970-01-01
      • 2016-08-14
      • 1970-01-01
      • 1970-01-01
      • 1970-01-01
      • 2021-01-22
      • 1970-01-01
      相关资源
      最近更新 更多