• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: EOObjectNotAvailableException: prepareForSaveWithCoordinator
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: EOObjectNotAvailableException: prepareForSaveWithCoordinator


  • Subject: Re: EOObjectNotAvailableException: prepareForSaveWithCoordinator
  • From: Stefan Klein <email@hidden>
  • Date: Fri, 17 Oct 2008 10:03:43 +0200

That's my problem, theirs no other exception in the log files. The exception seems to occurs every leap year, so i can't reproduce it.
Is there a way to catch the exception and get rid of the corrupt object and reload it?


Stefan


Lachlan Deck schrieb:
On 17/10/2008, at 6:51 AM, Stefan Klein wrote:

i got the following exception:

com.webobjects.eoaccess.EOObjectNotAvailableException: prepareForSaveWithCoordinator: Cannot save the object with globalID _EOIntegralKeyGlobalID[Benutzer (java.lang.Long)4559]. 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().
at com.webobjects.eoaccess.EODatabaseContext.prepareForSaveWithCoordinator(EODatabaseContext.java:5831)


at com.webobjects.eocontrol.EOObjectStoreCoordinator.saveChangesInEditingContext(EOObjectStoreCoordinator.java:409)

at com.webobjects.eocontrol.EOEditingContext.saveChanges(EOEditingContext.java:3187)


But I know that the object for this id exist, cause that user logged in many times before in that instance. The instance was running for several days without any problem.
After the exception occurs the first time, the user can't log in again in that instance. A login to the second instance did work.
After stopping and starting the first instance all works fine.


Does any one have a suggestion?

Check the logs. Probably had some exceptions that went unnoticed.

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


  • Follow-Ups:
    • Re: EOObjectNotAvailableException: prepareForSaveWithCoordinator
      • From: Lachlan Deck <email@hidden>
References: 
 >EOObjectNotAvailableException: prepareForSaveWithCoordinator (From: Stefan Klein <email@hidden>)
 >Re: EOObjectNotAvailableException: prepareForSaveWithCoordinator (From: Lachlan Deck <email@hidden>)

  • Prev by Date: Re: eogenerate ant task?
  • Next by Date: Re: eogenerate ant task?
  • Previous by thread: Re: EOObjectNotAvailableException: prepareForSaveWithCoordinator
  • Next by thread: Re: EOObjectNotAvailableException: prepareForSaveWithCoordinator
  • Index(es):
    • Date
    • Thread