Popular Posts

Tuesday, October 1, 2013

Problem faced while configuring Liferay with MySQL

Today, I faced an issue while I started configuring MySQL with Liferay 6.1.
In the logs I started getting following errors:
impossible to write to binary log since BINLOG_FORMAT=STATEMENT and at least one table uses a storage engine limited to row-based logging when transaction isolation level is READ COMMITTED or READ UNCOMMITTED
This issue is very common with MySQL version 5.6. because by default, BINLOG_FORMAT=STATEMENT here. I have changed it to ROW and I got rid of this error.

The command to be used :
mysql> SET GLOBAL binlog_format = 'ROW';


Now I have encountered another kind of problem. In logs it is started giving below error.

check the manual that corresponds to your MySQL server version for the right syntax to use near 'OPTION SQL_SELECT_LIMIT=DEFAULT.

 This error is due to mysql jdbc connector issue. We need to change the jar in {Liferay_home}/{TOMCAT_HOME}/lib/ext folder.

Steps to be followed:
1. Download latest MySQL connector jar from here. It will be an installer.
2. After installing this you will get the jar is stored under <Directory>:\Program Files (x86)\MySQL\MySQL Connector J
3. Take the jar and put that into {Liferay_home}/{TOMCAT_HOME}/lib/ext folder
4. Remove mysql.jar from this directory.
5. Rename the new jar to mysql.jar

The errors are gone.


No comments:

Post a Comment