Re: Cannot rollbackTransaction() while a fetch is in progress (Was: MySQL 5.0 - note)
Re: Cannot rollbackTransaction() while a fetch is in progress (Was: MySQL 5.0 - note)
- Subject: Re: Cannot rollbackTransaction() while a fetch is in progress (Was: MySQL 5.0 - note)
- From: Lachlan Deck <email@hidden>
- Date: Thu, 10 Jul 2008 14:51:00 +1000
Anyone else seen this or know why it happens?
On 09/07/2008, at 4:49 PM, Lachlan Deck wrote:
Hi there,
did you manage to track this one down? I've just started seeing this
today... confounding nuisance.
On 21/02/2008, at 1:45 AM, Simon McLean wrote:
Hi Kieran,
In the last couple of days we have been getting the following error
cropping up in a couple of places:
java.lang.Thread.run(Thread.java:613) Caused by:
com.webobjects.jdbcadaptor.JDBCAdaptorException: Cannot
rollbackTransaction() while a fetch is in progress at
com
.webobjects
.jdbcadaptor.JDBCContext.rollbackTransaction(JDBCContext.java:437)
at
com
.webobjects
.eoaccess.EODatabaseContext.rollbackChanges(EODatabaseContext.java:
6606) at
com
.webobjects
.eoaccess.EODatabaseContext.commitChanges(EODatabaseContext.java:
6482) at
com
.webobjects
.eocontrol
.EOObjectStoreCoordinator
.saveChangesInEditingContext(EOObjectStoreCoordinator.java:425) at
com
.webobjects
.eocontrol.EOEditingContext.saveChanges(EOEditingContext.java:3226)
at er.extensions.ERXEC._saveChanges(ERXEC.java:940) at
I'm wondering if your note about that change to MySQL behaviour is
the cause of this. We are on 5.0.50 and do not have the --
innodb_rollback_on_timeout set.
Have you ever seen this error ?
Thanks, Simon
On 18 Feb 2008, at 21:53, Kieran Kelleher wrote:
Any of you who use MySQL with InnoDB (you should be using
InnoDB!), then note the following change in the upgrade notes. I
would think you would want the whole transaction to be rolled back
on timeout.........
Incompatible change: As of MySQL 5.0.13, InnoDB rolls back only
the last statement on a transaction timeout. In MySQL 5.0.32, a
new option, --innodb_rollback_on_timeout, causes InnoDB to abort
and roll back the entire transaction if a transaction timeout
occurs (the same behavior as in MySQL 4.1).
.... anyway, just an FYI (if I am reading this correctly) to those
who don't want a partial editingContext.saveChanges() to ever
happen in the event your WOA app server dies in the middle of a
transaction.
Regards, Kieran
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
with regards,
--
Lachlan Deck
with regards,
--
Lachlan Deck
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden