Re: EOF WTF?
Re: EOF WTF?
- Subject: Re: EOF WTF?
- From: Helge Städtler <email@hidden>
- Date: Thu, 14 Jul 2005 18:30:53 +0200
i think this issue was resolved in WO5.2.3. i had the very same issues
before 5.2.2 came out i think. but I am not yet running 5.3 so... are you
running the app with concurrent requesthandling "on"? if yes, you should
really LOCK/UNLOCK the editingcontexts properly.
i also experienced problems with editingcontext, if you call
session.terminate() directly instead i set the session-timeout to zero which
does the same, but some WO-Thread is doin it for me later when the session
is checked in.
perhaps you should also check if it is a special relationship you are
working with which needs a certain order of setting things. how about the
model-info on this relationship e.g.
just check everything which might tangle the relationship.
try to call these methods in your appliction constructor to debug locking
failures.
NSLog.setAllowedDebugGroups(
NSLog.DebugGroupRequestHandling+NSLog.DebugGroupMultithreading );
NSLog.setAllowedDebugLevel( NSLog.DebugLevelInformational );
more about that here:
http://wocode.com/cgi-bin/WebObjects/WOCode.woa/2/wa/ShareCodeItem?itemId=32
0
regards,
helge
Am 14.07.2005 17:35 Uhr schrieb "Rick Innis" unter <email@hidden> / On
14.07.2005 17:35 Uhr "Rick Innis" wrote using address <email@hidden>:
> Can anyone help explain this exception from EOF?
>
> prepareForSaveWithCoordinator: Cannot save the object with globalID
> _EOIntegralKeyGlobalID[Systemuser (java.math.BigDecimal)1000085]. The
> row referenced by this globalID was missing from the database at the
> time a fetch was attempted. Either it was removed from the database
> after this application got a pointer to it, or there is a referential
> integrity problem with your database. To be notified when fetches
> fail, implement a delegate on EODatabaseContext that responds to
> databaseContextFailedToFetchObject().
>
> I understand what it's telling me, and it's perfectly right- there is
> no Systemuser object with a key of 1000085.
>
> There is, however, one with a key of 1000086 which is actually the
> object I expect to have. The Systemuser object was created, saved,
> and refreshed in a previous WebObject, which stores it in the session
> and invokes the one that throws this exception, which is thrown when
> trying to save it after an update.
>
> I've resolved the issue by using an EOFetchSpecification to retrieve
> the Systemuser object in the second page, but if anyone has any
> insight into why this exception is occurring I'd like to hear it.
> (The backend DB is FrontBase, and I'm using WO 5.3 on Tiger, in case
> these details make any difference.)
>
> --Rick.
>
> _______________________________________________
> 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
| References: | |
| | >EOF WTF? (From: Rick Innis <email@hidden>) |