Problem with primary keys during loading with a multi-instance WebObjects app in Leo/WO 5.4.1
Problem with primary keys during loading with a multi-instance WebObjects app in Leo/WO 5.4.1
- Subject: Problem with primary keys during loading with a multi-instance WebObjects app in Leo/WO 5.4.1
- From: Irina Popova <email@hidden>
- Date: Thu, 24 Apr 2008 16:22:08 +0300
| Hi all,
To start, I apologize for the cross post (I've already posted the problem to the FrontBase developers' list), but thought that someone else here has come across the same problem:
The problem we have observed only after we switched to Leo/WO 5.4.1.
The set up: Mac OS 10.5.2 Server WebObjects 5.4.1 FrontBase 4.2.8
We have a WO app, which is used to load data in the database. The loading is done by a direct action. The editing context is a new EOEditingContext() for each direct action and is disposed at the end. At the end of the direct action we have saveChanges() and as a result multiple INSERT statements are generated for the DB. The application is running with multiple instances.
From time to time we get exceptions like the following:
Possible EO validation error: Exception condition 358. Integrity constraint violation (PRIMARY KEY, TT_INVOICE_ENTRY._C0000000394(ID=1005219)
This is a primary key violation. Primary keys are automatically generated by FB. From the logs I can say that a row with that primary key has already been inserted in the database by one of the other instances of the application.
The same multi-instance set up has been running with no problems on Tiger/WO 5.3.
Thanks for any ideas.
regards, Irina
Irina Popova Tuparev Technologies 3 Sofijski Geroj Str., Entr.2, Apt.27 1612 Sofia Bulgaria
phone: +359 2 950 15 05 fax: +359 2 953 22 16
|
_______________________________________________
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