Re: Project Wonder ERXEC Locking problem
Re: Project Wonder ERXEC Locking problem
- Subject: Re: Project Wonder ERXEC Locking problem
- From: Mike Schrag <email@hidden>
- Date: Tue, 25 Nov 2008 13:54:17 -0500
QUESTIONS:
- Should we use manual locking/unlocking inside the thread?
- Should we even bother to use ERXEC inside the thread? Maybe just use the original WO EOEditingContext
- Is this error causing us any problems? Should we ignore it? How can we configure Wonder or Log4j properties to mask the error if it is informational only?
There is some debate about this topic, but one option is to set er.extensions.ERXThreadStorage.useInheritableThreadLocal=false to make ERXThreadStorage not inherit ThreadLocals. I put this option in quite a while ago, but left it defaulted off for fear of ruining everything. There is a thread discussing this and other related issues on the wonder list from maybe last week or the week before.
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