Re: "Cannot obtain globalId for an object which..."
Re: "Cannot obtain globalId for an object which..."
- Subject: Re: "Cannot obtain globalId for an object which..."
- From: Kaj Hejer <email@hidden>
- Date: Sat, 15 Nov 2003 21:20:33 +0100
At 12:00 -0800 15-11-03, Chuck Hill wrote:
The "access with no lock" warning is not always right. The first time a
EODatabaseContext connects to a database an "access with no lock" warning
is output from the EODatabaseContext constructor. This message can be
safely ignored. If the trace contains EODatabaseContext.<init> then you
can ignore it.
One thing to try is to log out the "id" (e.g. the EOEditingContext@3273cc
part) of each editing context when it is created
NSLog.out.appendln("X created ec " + editingContext());
That way you have a better chance of tracking down which ones are involved in
object's editingContext: com.webobjects.eocontrol.EOEditingContext@3273cc,
databaseContext's active editingContext:
com.webobjects.eocontrol.EOEditingContext@53ab04
Thaks! Good idea! Done! :)
That may provide the essential clue.
I also trust that you are locking the ec in your long response page.
Yes, I do!
-Kaj :)
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.