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

Deadlocks


  • Subject: Deadlocks
  • From: Simon McLean <email@hidden>
  • Date: Wed, 5 Sep 2007 23:01:08 +0100

Hi -

We're experiencing some pretty bad deadlock issues at the moment and I'm pretty convinced it's down to EC lock abuse.

Can anyone confirm that if we follow these rules:

** If you do want all that Wonder magic and love:
1) extend ERXApplication
2) extend ERXSession
3) use ERXEC.newEditingContext() instead of new EOEditingContext()
4) Add to Properties:
er.extensions.ERXApplication.useEditingContextUnlocker=true
er.extensions.ERXEC.defaultAutomaticLockUnlock=true
er.extensions.ERXEC.useSharedEditingContext=false
er.extensions.ERXEC.defaultCoalesceAutoLocks=true"

... we should never have to manually lock or unlock an EC ? Or put another way, when using these rules is there any situation that we would have to call ec.lock() or ec.unlock() in our code ?

Thanks, Simon
 _______________________________________________
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: Deadlocks
      • From: Chuck Hill <email@hidden>
    • Re: Deadlocks
      • From: Guido Neitzer <email@hidden>
  • Prev by Date: Re: Get Sessions from Application
  • Next by Date: Re: Deadlocks
  • Previous by thread: Re: Get Sessions from Application
  • Next by thread: Re: Deadlocks
  • Index(es):
    • Date
    • Thread