Re: JDBCChannel method failed to update
Re: JDBCChannel method failed to update
- Subject: Re: JDBCChannel method failed to update
- From: shaun <email@hidden>
- Date: Tue, 25 Jul 2006 18:12:12 +0930
Hi,
Corin Lawson wrote:
Hi List,
As volume has increased on our woapp so has the occurrence of this
particular error, below. I am using WO 5.2.4 with MySQL 5.0.
com.webobjects.eoaccess.EOGeneralAdaptorException:
updateValuesInRowDescribedByQualifier --
com.webobjects.jdbcadaptor.JDBCChannel method failed to update row in
database
at
com.webobjects.eoaccess.EODatabaseContext._exceptionWithDatabaseContextI
nformationAdded(EODatabaseContext.java:4685)
at com.webobjects.eoaccess.EODatabaseContext.performChanges
(EODatabaseContext.java:6393)
at
com.webobjects.eocontrol.EOObjectStoreCoordinator.saveChangesInEditingCo
ntext(EOObjectStoreCoordinator.java:415)
at com.webobjects.eocontrol.EOEditingContext.saveChanges
(EOEditingContext.java:3226)
We are currently looking into any network issues that could be causing
communication problems between the two servers (the one with the woapp
and the other with the database). Can anyone provide light to this
exception?
Optimistic locking failure perhaps. ie, One client trying to modify a
row that has been deleted or modified by another client. The more
clients accessing making modifications at the same time the more likely
this is to occur. Check which attributes are used for locking on the
entity that this occurs on to see if its likely being modified by more
than one client. I assume you are able to pin-point the entity or the
component at least. Catching this exception, then getting the user to
handle the modification somehow is probably the solution you should
consider rather than unchecking attributes used for locking.
HTH.
- shaun
_______________________________________________
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