• 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
EODatabaseContext locking situation
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

EODatabaseContext locking situation


  • Subject: EODatabaseContext locking situation
  • From: Ken Anderson <email@hidden>
  • Date: Tue, 6 Nov 2007 09:17:38 -0500

Everyone,

I have a significantly multi-threaded app that's having a locking problem with EODatabaseContext. One thread has successfully locked an EC and attempted a query. In the stack trace of that thread, after it has locked the EC, it goes to do a fetch, and this is the top of the stack trace:

Object.wait(long) line: not available [native method]
NSRecursiveLock(Object).wait() line: 474
NSRecursiveLock.lock() line: 72
EODatabaseContext.lock() line: 1973
EOObjectStoreCoordinator.addCooperatingObjectStore (EOCooperatingObjectStore) line: 130
EODatabaseChannel.setCurrentEditingContext(EOEditingContext) line:166



It stays here forever. I've checked the few places I actually lock the DB context, and they're properly protected, and no thread is anywhere else in EOF but this one.


Any thoughts??  This is 5.3...

Thanks,
Ken

_______________________________________________
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: EODatabaseContext locking situation
      • From: Chuck Hill <email@hidden>
  • Prev by Date: delete rule and class property
  • Next by Date: How to create WO Project on Leopard
  • Previous by thread: Re: delete rule and class property
  • Next by thread: Re: EODatabaseContext locking situation
  • Index(es):
    • Date
    • Thread