Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Re: Unlocking thread not owner deadlock from an Ajax Updating Container

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Unlocking thread not owner deadlock from an Ajax Updating Container

Subject: Re: Unlocking thread not owner deadlock from an Ajax Updating Container
From: Paul Stringer <email@hidden>
Date: Sun, 21 Dec 2008 15:13:05 +0000

1) autolocking flags are good
2) the finger definitely seems to keep ending up at using an SEC

I'm going to rework and get rid of traces of the SEC and see if it goes away.

Paul S

I'm pretty sure I have nothing else happening in any of my own self created threads. I've disabled concurrent request handling. EditingContexts are created from ERXEC.newEditingContext() with one tied to each user session . I'm not using defaultEditingContext() and have ERXECs autolocking turned on. I am using a shared editing context for some read only stuff elsewhere in the app.

1) make sure you have all the necessary autolocking flags enabled, or the newer safeLocking variant 2) the only deadlocks i have seen with wonder locking are when SEC were involved

ms

_______________________________________________
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



Prev by Date:
Re: [OT] New WO Years Resolutions.

Next by Date:
SSDD build problem after upgrade

Previous by thread:
Fwd: Shark memory allocation trace error

Next by thread:
SSDD build problem after upgrade

Index(es):

Date
Thread