Thanks Simon.

On 10/07/2008, at 1:02 AM, Simon McLean wrote:

sorry lachlan, no i didn't. but it has since gone away so maybe just a framework version issue. we haven't updated mysql or the j connector.

Simon

On 9 Jul 2008, at 07:49, 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      (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/simon_mclean%40mac.com

This email sent to [EMAIL PROTECTED]

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/lachlan.deck%40gmail.com

This email sent to [EMAIL PROTECTED]

with regards,
--

Lachlan Deck



with regards,
--

Lachlan Deck



_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [EMAIL PROTECTED]

Reply via email to