On Oct 7, 2009, at 9:06 PM, Kieran Kelleher wrote:
Thread t...@76291: (state = BLOCKED)
- sun.misc.Unsafe.park(boolean, long) @bci=0 (Interpreted frame)
Let me guess, you have just updated wonder, right?
The reason I'm saying this is that I've spent the day solving a
similar deadlock, similar on the 'unsafe park' at least.
I am using docmosis (http://docmosis.com/) to generate PDFs and .DOCs.
I've cooked up a simple 'data provider' that uses KVC to supply the
data on the templates. I just pass an EO to it and presto. Since all
my code is i the request/response loop, I never gave it a second
thought. It turns out that a thread is spun to do the actual work, and
the latest changes in locking behaviour in wonder exposed the faulty
assumptions.
I now pass a GlobalID and lazily initialize an EditingContetx and
fetch the EO on the first access to the data provider, that way every
acces is on the same thread.
So my point really is that Anjo's latest changes on ERXEC might have
exposed something, or there is a bug on those changes (naaaaahhh)
Regards,
Henrique Gomes
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
