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: Chuck Hill <email@hidden>
- Date: Mon, 08 Dec 2003 11:21:50 -0800
- Organization: Global Village Consulting, Inc.
I'm pretty sure that relating objects in different editing contexts
has always (in the Java versions at least) given that error. That is
where I am most familiar with it. ;-)
Chuck
Kaj Hejer wrote:
At 14:33 +0100 14-11-03, Kaj Hejer wrote:
At 12:56 -0700 10-06-03, Chuck Hill wrote:
Hi Kaj,
First off,
I also get a bit confused about what "databaseContext's active
editingContext" mean.
When an EC starts to do anything outside of its sandbox (fetching and
saving), it locks the database context(s) that it is using. Only one
EC can lock a database context at a time. When an EC locks a
database context that EC becomes the database context's active
editing context.
Is it possible that this has been related, in code, to an Pasient in
a different editing context?
Hi!
Thank again for this info!
Last time I posted about this issue it was on WO5.1.3. Now I have this
issue on WO5.2.1.
The stacktrace is available at
http://folk.uio.no/kajh/tmp/bug20031114.txt
We use only session.defaultEditingContext and childEditingContext of
this ec. We lock/unlock our childEditingContext in session.awake/sleep.
As far as I can see we don't have any relatinships between objects in
different editingContext.
This issue seems to happen at random (1 of 30 times? I havn't yet any
reliable data for how often it occur).
I havn't yet testet this on WO5.2.2, but we are goding to do that real
soon!
Config: WO5.2.1, solaris, java 1.3.1.
Hi!
Today I got this "Cannot obtain globalId for an object which..."
exception on WO5.2.2 and java1.4.1.
I managed to isolate this issue and in this case the source for the
problem was that I tried to use
addObjectToBothSidesOfRelationshipWithKey on two objects in different
editingContexts, and then I got this exception on the next saveChanges.
Earlier (WO5.1.3) I think this gave a NullPointerException on
saveChanges, but it looks like that has changes in WO5.2.2.
The original problem that I had when I started this thread seems to be a
different story and don't seems to be related to objects in different
editingContexts.
-Kaj :)
--
Chuck Hill email@hidden
Global Village Consulting Inc. http://www.global-village.net
Progress is the mother of all problems.
- G. K. Chesterton
_______________________________________________
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.