Mysql problems

[Dean Pullen]

After restarting my dev machine, where upon Ofbiz was previously
working, I'm now getting these errors for every DB call from ./ant run


java.lang.Exception: Failure in storeByCondition operation for entity
[JobSandbox]: org.ofbiz.entity.GenericDataSourceException: Generic
Entity Exception occured in updateByCondition (SQL Exception while
executing the following:UPDATE JOB_SANDBOX SET RUN_BY_INSTANCE_ID = ?,
STATUS_ID = ? WHERE ((RUN_TIME <= '2012-02-22 10:16:46.439' AND
START_DATE_TIME IS NULL AND CANCEL_DATE_TIME IS NULL AND
RUN_BY_INSTANCE_ID IS NULL) AND (POOL_ID IS NULL OR POOL_ID = 'pool'))
(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.)).
Rolling back transaction.
      [java]
org.ofbiz.entity.transaction.TransactionUtil.setRollbackOnly(TransactionUtil.java:370)
      [java]
org.ofbiz.entity.transaction.TransactionUtil.rollback(TransactionUtil.java:312)
      [java]
org.ofbiz.entity.GenericDelegator.storeByCondition(GenericDelegator.java:1300)
      [java]
org.ofbiz.entity.GenericDelegator.storeByCondition(GenericDelegator.java:1261)
      [java] org.ofbiz.service.job.JobManager.poll(JobManager.java:157)
      [java] org.ofbiz.service.job.JobPoller.run(JobPoller.java:90)
      [java] java.lang.Thread.run(Thread.java:680)

Can anyone help me with this please?

Many thanks,

Dean.

[Sascha Rodekamp-3]

Hey
Try to empty the Job_Sandbox table. That should solve the problem.

Have a good day
Sascha

Am 22.02.2012 um 11:23 schrieb Dean Pullen <[hidden email]>:

> After restarting my dev machine, where upon Ofbiz was previously working, I'm now getting these errors for every DB call from ./ant run
>
>
> java.lang.Exception: Failure in storeByCondition operation for entity [JobSandbox]: org.ofbiz.entity.GenericDataSourceException: Generic Entity Exception occured in updateByCondition (SQL Exception while executing the following:UPDATE JOB_SANDBOX SET RUN_BY_INSTANCE_ID = ?, STATUS_ID = ? WHERE ((RUN_TIME <= '2012-02-22 10:16:46.439' AND START_DATE_TIME IS NULL AND CANCEL_DATE_TIME IS NULL AND RUN_BY_INSTANCE_ID IS NULL) AND (POOL_ID IS NULL OR POOL_ID = 'pool')) (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.)). Rolling back transaction.
>     [java] org.ofbiz.entity.transaction.TransactionUtil.setRollbackOnly(TransactionUtil.java:370)
>     [java] org.ofbiz.entity.transaction.TransactionUtil.rollback(TransactionUtil.java:312)
>     [java] org.ofbiz.entity.GenericDelegator.storeByCondition(GenericDelegator.java:1300)
>     [java] org.ofbiz.entity.GenericDelegator.storeByCondition(GenericDelegator.java:1261)
>     [java] org.ofbiz.service.job.JobManager.poll(JobManager.java:157)
>     [java] org.ofbiz.service.job.JobPoller.run(JobPoller.java:90)
>     [java] java.lang.Thread.run(Thread.java:680)
>
> Can anyone help me with this please?
>
> Many thanks,
>
> Dean.

[Dean Pullen]

Thanks for the reply, but still seeing the same exceptions.

[java] [TransactionUtil.setRollbackOnly] Calling transaction
setRollbackOnly; this stack trace shows where this is happening:
      [java] Exception: java.lang.Exception
      [java] Message: Failure in storeByCondition operation for entity
[JobSandbox]: org.ofbiz.entity.GenericDataSourceException: Generic
Entity Exception occured in updateByCondition (SQL Exception while
executing the following:UPDATE JOB_SANDBOX SET RUN_BY_INSTANCE_ID = ?,
STATUS_ID = ? WHERE ((RUN_TIME <= '2012-02-22 11:19:04.663' AND
START_DATE_TIME IS NULL AND CANCEL_DATE_TIME IS NULL AND
RUN_BY_INSTANCE_ID IS NULL) AND (POOL_ID IS NULL OR POOL_ID = 'pool'))
(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.)).
Rolling back transaction.



On 22/02/2012 11:02, Sascha Rodekamp wrote:

> Hey
> Try to empty the Job_Sandbox table. That should solve the problem.
>
> Have a good day
> Sascha
>
> Am 22.02.2012 um 11:23 schrieb Dean Pullen<[hidden email]>:
>
>> After restarting my dev machine, where upon Ofbiz was previously working, I'm now getting these errors for every DB call from ./ant run
>>
>>
>> java.lang.Exception: Failure in storeByCondition operation for entity [JobSandbox]: org.ofbiz.entity.GenericDataSourceException: Generic Entity Exception occured in updateByCondition (SQL Exception while executing the following:UPDATE JOB_SANDBOX SET RUN_BY_INSTANCE_ID = ?, STATUS_ID = ? WHERE ((RUN_TIME<= '2012-02-22 10:16:46.439' AND START_DATE_TIME IS NULL AND CANCEL_DATE_TIME IS NULL AND RUN_BY_INSTANCE_ID IS NULL) AND (POOL_ID IS NULL OR POOL_ID = 'pool')) (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.)). Rolling back transaction.
>>      [java] org.ofbiz.entity.transaction.TransactionUtil.setRollbackOnly(TransactionUtil.java:370)
>>      [java] org.ofbiz.entity.transaction.TransactionUtil.rollback(TransactionUtil.java:312)
>>      [java] org.ofbiz.entity.GenericDelegator.storeByCondition(GenericDelegator.java:1300)
>>      [java] org.ofbiz.entity.GenericDelegator.storeByCondition(GenericDelegator.java:1261)
>>      [java] org.ofbiz.service.job.JobManager.poll(JobManager.java:157)
>>      [java] org.ofbiz.service.job.JobPoller.run(JobPoller.java:90)
>>      [java] java.lang.Thread.run(Thread.java:680)
>>
>> Can anyone help me with this please?
>>
>> Many thanks,
>>
>> Dean.

[Sascha Rodekamp-3]

Hm ok I had similar issues when there where old corrupted jobs in the sandbox.

Am 22.02.2012 um 12:20 schrieb Dean Pullen <[hidden email]>:

> Thanks for the reply, but still seeing the same exceptions.
>
> [java] [TransactionUtil.setRollbackOnly] Calling transaction setRollbackOnly; this stack trace shows where this is happening:
>     [java] Exception: java.lang.Exception
>     [java] Message: Failure in storeByCondition operation for entity [JobSandbox]: org.ofbiz.entity.GenericDataSourceException: Generic Entity Exception occured in updateByCondition (SQL Exception while executing the following:UPDATE JOB_SANDBOX SET RUN_BY_INSTANCE_ID = ?, STATUS_ID = ? WHERE ((RUN_TIME <= '2012-02-22 11:19:04.663' AND START_DATE_TIME IS NULL AND CANCEL_DATE_TIME IS NULL AND RUN_BY_INSTANCE_ID IS NULL) AND (POOL_ID IS NULL OR POOL_ID = 'pool')) (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.)). Rolling back transaction.
>
>
>
> On 22/02/2012 11:02, Sascha Rodekamp wrote:
>> Hey
>> Try to empty the Job_Sandbox table. That should solve the problem.
>>
>> Have a good day
>> Sascha
>>
>> Am 22.02.2012 um 11:23 schrieb Dean Pullen<[hidden email]>:
>>
>>> After restarting my dev machine, where upon Ofbiz was previously working, I'm now getting these errors for every DB call from ./ant run
>>>
>>>
>>> java.lang.Exception: Failure in storeByCondition operation for entity [JobSandbox]: org.ofbiz.entity.GenericDataSourceException: Generic Entity Exception occured in updateByCondition (SQL Exception while executing the following:UPDATE JOB_SANDBOX SET RUN_BY_INSTANCE_ID = ?, STATUS_ID = ? WHERE ((RUN_TIME<= '2012-02-22 10:16:46.439' AND START_DATE_TIME IS NULL AND CANCEL_DATE_TIME IS NULL AND RUN_BY_INSTANCE_ID IS NULL) AND (POOL_ID IS NULL OR POOL_ID = 'pool')) (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.)). Rolling back transaction.
>>>     [java] org.ofbiz.entity.transaction.TransactionUtil.setRollbackOnly(TransactionUtil.java:370)
>>>     [java] org.ofbiz.entity.transaction.TransactionUtil.rollback(TransactionUtil.java:312)
>>>     [java] org.ofbiz.entity.GenericDelegator.storeByCondition(GenericDelegator.java:1300)
>>>     [java] org.ofbiz.entity.GenericDelegator.storeByCondition(GenericDelegator.java:1261)
>>>     [java] org.ofbiz.service.job.JobManager.poll(JobManager.java:157)
>>>     [java] org.ofbiz.service.job.JobPoller.run(JobPoller.java:90)
>>>     [java] java.lang.Thread.run(Thread.java:680)
>>>
>>> Can anyone help me with this please?
>>>
>>> Many thanks,
>>>
>>> Dean.

[Dean Pullen]

Can anyone else help? Completely stuck when trying to start the server...

Dean.

On 22/02/2012 11:36, Sascha Rodekamp wrote:

> Hm ok I had similar issues when there where old corrupted jobs in the sandbox.
>
> Am 22.02.2012 um 12:20 schrieb Dean Pullen<[hidden email]>:
>
>> Thanks for the reply, but still seeing the same exceptions.
>>
>> [java] [TransactionUtil.setRollbackOnly] Calling transaction setRollbackOnly; this stack trace shows where this is happening:
>>      [java] Exception: java.lang.Exception
>>      [java] Message: Failure in storeByCondition operation for entity [JobSandbox]: org.ofbiz.entity.GenericDataSourceException: Generic Entity Exception occured in updateByCondition (SQL Exception while executing the following:UPDATE JOB_SANDBOX SET RUN_BY_INSTANCE_ID = ?, STATUS_ID = ? WHERE ((RUN_TIME<= '2012-02-22 11:19:04.663' AND START_DATE_TIME IS NULL AND CANCEL_DATE_TIME IS NULL AND RUN_BY_INSTANCE_ID IS NULL) AND (POOL_ID IS NULL OR POOL_ID = 'pool')) (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.)). Rolling back transaction.
>>
>>
>>
>> On 22/02/2012 11:02, Sascha Rodekamp wrote:
>>> Hey
>>> Try to empty the Job_Sandbox table. That should solve the problem.
>>>
>>> Have a good day
>>> Sascha
>>>
>>> Am 22.02.2012 um 11:23 schrieb Dean Pullen<[hidden email]>:
>>>
>>>> After restarting my dev machine, where upon Ofbiz was previously working, I'm now getting these errors for every DB call from ./ant run
>>>>
>>>>
>>>> java.lang.Exception: Failure in storeByCondition operation for entity [JobSandbox]: org.ofbiz.entity.GenericDataSourceException: Generic Entity Exception occured in updateByCondition (SQL Exception while executing the following:UPDATE JOB_SANDBOX SET RUN_BY_INSTANCE_ID = ?, STATUS_ID = ? WHERE ((RUN_TIME<= '2012-02-22 10:16:46.439' AND START_DATE_TIME IS NULL AND CANCEL_DATE_TIME IS NULL AND RUN_BY_INSTANCE_ID IS NULL) AND (POOL_ID IS NULL OR POOL_ID = 'pool')) (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.)). Rolling back transaction.
>>>>      [java] org.ofbiz.entity.transaction.TransactionUtil.setRollbackOnly(TransactionUtil.java:370)
>>>>      [java] org.ofbiz.entity.transaction.TransactionUtil.rollback(TransactionUtil.java:312)
>>>>      [java] org.ofbiz.entity.GenericDelegator.storeByCondition(GenericDelegator.java:1300)
>>>>      [java] org.ofbiz.entity.GenericDelegator.storeByCondition(GenericDelegator.java:1261)
>>>>      [java] org.ofbiz.service.job.JobManager.poll(JobManager.java:157)
>>>>      [java] org.ofbiz.service.job.JobPoller.run(JobPoller.java:90)
>>>>      [java] java.lang.Thread.run(Thread.java:680)
>>>>
>>>> Can anyone help me with this please?
>>>>
>>>> Many thanks,
>>>>
>>>> Dean.

[Anne Jessel]

Hi Dean

Google suggested this:

http://bugs.mysql.com/bug.php?id=62493

which sounds like it matches your symptoms. So I'd suggest checking for a
broken mysql config.

Cheers,
Anne.

On 24 February 2012 04:14, Dean Pullen <[hidden email]> wrote:

> Can anyone else help? Completely stuck when trying to start the server...
>
> Dean.
>
>
> On 22/02/2012 11:36, Sascha Rodekamp wrote:
>
>> Hm ok I had similar issues when there where old corrupted jobs in the
>> sandbox.
>>
>> Am 22.02.2012 um 12:20 schrieb Dean Pullen<dean.pullen@semantico.**com<[hidden email]>
>> >:
>>
>>  Thanks for the reply, but still seeing the same exceptions.
>>>
>>> [java] [TransactionUtil.**setRollbackOnly] Calling transaction
>>> setRollbackOnly; this stack trace shows where this is happening:
>>>     [java] Exception: java.lang.Exception
>>>     [java] Message: Failure in storeByCondition operation for entity
>>> [JobSandbox]: org.ofbiz.entity.**GenericDataSourceException: Generic
>>> Entity Exception occured in updateByCondition (SQL Exception while
>>> executing the following:UPDATE JOB_SANDBOX SET RUN_BY_INSTANCE_ID = ?,
>>> STATUS_ID = ? WHERE ((RUN_TIME<= '2012-02-22 11:19:04.663' AND
>>> START_DATE_TIME IS NULL AND CANCEL_DATE_TIME IS NULL AND RUN_BY_INSTANCE_ID
>>> IS NULL) AND (POOL_ID IS NULL OR POOL_ID = 'pool')) (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.)). Rolling back transaction.
>>>
>>>
>>>
>>> On 22/02/2012 11:02, Sascha Rodekamp wrote:
>>>
>>>> Hey
>>>> Try to empty the Job_Sandbox table. That should solve the problem.
>>>>
>>>> Have a good day
>>>> Sascha
>>>>
>>>> Am 22.02.2012 um 11:23 schrieb Dean Pullen<dean.pullen@semantico.**com<[hidden email]>
>>>> >:
>>>>
>>>>  After restarting my dev machine, where upon Ofbiz was previously
>>>>> working, I'm now getting these errors for every DB call from ./ant run
>>>>>
>>>>>
>>>>> java.lang.Exception: Failure in storeByCondition operation for entity
>>>>> [JobSandbox]: org.ofbiz.entity.**GenericDataSourceException: Generic
>>>>> Entity Exception occured in updateByCondition (SQL Exception while
>>>>> executing the following:UPDATE JOB_SANDBOX SET RUN_BY_INSTANCE_ID = ?,
>>>>> STATUS_ID = ? WHERE ((RUN_TIME<= '2012-02-22 10:16:46.439' AND
>>>>> START_DATE_TIME IS NULL AND CANCEL_DATE_TIME IS NULL AND RUN_BY_INSTANCE_ID
>>>>> IS NULL) AND (POOL_ID IS NULL OR POOL_ID = 'pool')) (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.)). Rolling back transaction.
>>>>>     [java] org.ofbiz.entity.transaction.**TransactionUtil.**
>>>>> setRollbackOnly(**TransactionUtil.java:370)
>>>>>     [java] org.ofbiz.entity.transaction.**TransactionUtil.rollback(**
>>>>> TransactionUtil.java:312)
>>>>>     [java] org.ofbiz.entity.**GenericDelegator.**storeByCondition(**
>>>>> GenericDelegator.java:1300)
>>>>>     [java] org.ofbiz.entity.**GenericDelegator.**storeByCondition(**
>>>>> GenericDelegator.java:1261)
>>>>>     [java] org.ofbiz.service.job.**JobManager.poll(JobManager.**
>>>>> java:157)
>>>>>     [java] org.ofbiz.service.job.**JobPoller.run(JobPoller.java:**90)
>>>>>     [java] java.lang.Thread.run(Thread.**java:680)
>>>>>
>>>>> Can anyone help me with this please?
>>>>>
>>>>> Many thanks,
>>>>>
>>>>> Dean.
>>>>>
>>>>

--
Coherent Software Australia Pty Ltd
PO Box 2773
Cheltenham Vic 3192
Phone: [phone]
Fax: [phone]
Web: http://www.cohsoft.com.au/
Email: [hidden email]

Bonsai ERP, the all-inclusive ERP system
http://www.bonsaierp.com.au/

[Dean Pullen]

Cheers Anne. For some reason, my googling gave me very little!

I've uncommented the bin_log_format row in my.ini, to:

# binary logging format - mixed recommended
binlog_format=mixed

I think mysql didn't pick up my.ini originally and this is why, on a
reboot, it was then failing as it had found the new config.

Thanks.

On 23/02/2012 22:54, Anne wrote:

> Hi Dean
>
> Google suggested this:
>
> http://bugs.mysql.com/bug.php?id=62493
>
> which sounds like it matches your symptoms. So I'd suggest checking for a
> broken mysql config.
>
> Cheers,
> Anne.
>
> On 24 February 2012 04:14, Dean Pullen<[hidden email]>  wrote:
>
>> Can anyone else help? Completely stuck when trying to start the server...
>>
>> Dean.
>>
>>
>> On 22/02/2012 11:36, Sascha Rodekamp wrote:
>>
>>> Hm ok I had similar issues when there where old corrupted jobs in the
>>> sandbox.
>>>
>>> Am 22.02.2012 um 12:20 schrieb Dean Pullen<dean.pullen@semantico.**com<[hidden email]>
>>>> :
>>>   Thanks for the reply, but still seeing the same exceptions.
>>>> [java] [TransactionUtil.**setRollbackOnly] Calling transaction
>>>> setRollbackOnly; this stack trace shows where this is happening:
>>>>      [java] Exception: java.lang.Exception
>>>>      [java] Message: Failure in storeByCondition operation for entity
>>>> [JobSandbox]: org.ofbiz.entity.**GenericDataSourceException: Generic
>>>> Entity Exception occured in updateByCondition (SQL Exception while
>>>> executing the following:UPDATE JOB_SANDBOX SET RUN_BY_INSTANCE_ID = ?,
>>>> STATUS_ID = ? WHERE ((RUN_TIME<= '2012-02-22 11:19:04.663' AND
>>>> START_DATE_TIME IS NULL AND CANCEL_DATE_TIME IS NULL AND RUN_BY_INSTANCE_ID
>>>> IS NULL) AND (POOL_ID IS NULL OR POOL_ID = 'pool')) (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.)). Rolling back transaction.
>>>>
>>>>
>>>>
>>>> On 22/02/2012 11:02, Sascha Rodekamp wrote:
>>>>
>>>>> Hey
>>>>> Try to empty the Job_Sandbox table. That should solve the problem.
>>>>>
>>>>> Have a good day
>>>>> Sascha
>>>>>
>>>>> Am 22.02.2012 um 11:23 schrieb Dean Pullen<dean.pullen@semantico.**com<[hidden email]>
>>>>>> :
>>>>>   After restarting my dev machine, where upon Ofbiz was previously
>>>>>> working, I'm now getting these errors for every DB call from ./ant run
>>>>>>
>>>>>>
>>>>>> java.lang.Exception: Failure in storeByCondition operation for entity
>>>>>> [JobSandbox]: org.ofbiz.entity.**GenericDataSourceException: Generic
>>>>>> Entity Exception occured in updateByCondition (SQL Exception while
>>>>>> executing the following:UPDATE JOB_SANDBOX SET RUN_BY_INSTANCE_ID = ?,
>>>>>> STATUS_ID = ? WHERE ((RUN_TIME<= '2012-02-22 10:16:46.439' AND
>>>>>> START_DATE_TIME IS NULL AND CANCEL_DATE_TIME IS NULL AND RUN_BY_INSTANCE_ID
>>>>>> IS NULL) AND (POOL_ID IS NULL OR POOL_ID = 'pool')) (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.)). Rolling back transaction.
>>>>>>      [java] org.ofbiz.entity.transaction.**TransactionUtil.**
>>>>>> setRollbackOnly(**TransactionUtil.java:370)
>>>>>>      [java] org.ofbiz.entity.transaction.**TransactionUtil.rollback(**
>>>>>> TransactionUtil.java:312)
>>>>>>      [java] org.ofbiz.entity.**GenericDelegator.**storeByCondition(**
>>>>>> GenericDelegator.java:1300)
>>>>>>      [java] org.ofbiz.entity.**GenericDelegator.**storeByCondition(**
>>>>>> GenericDelegator.java:1261)
>>>>>>      [java] org.ofbiz.service.job.**JobManager.poll(JobManager.**
>>>>>> java:157)
>>>>>>      [java] org.ofbiz.service.job.**JobPoller.run(JobPoller.java:**90)
>>>>>>      [java] java.lang.Thread.run(Thread.**java:680)
>>>>>>
>>>>>> Can anyone help me with this please?
>>>>>>
>>>>>> Many thanks,
>>>>>>
>>>>>> Dean.
>>>>>>
>