Hi, Ofbiz is running fine on my machine with MySQL and no replication.
It used to run fine on our soon to be production machine with no replication. Now that replication is turned on for all databases on the machine - other databases besides Ofbiz as well - get a ton of errors when starting Ofbiz to the effect that binary logging is not being handled, CPU maxes out at 100% and grinds the server. tons of messages like this: (Binary logging not possible. Message: Transaction level 'READ-COMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT')). Rolling back transaction. We really need replication for our DR and I am hoping that there is a nifty configuration fix for this. Has anyone run into this issue? Thanks James
