Re: Object with globalID could not be found in the database, when it is there ??
Re: Object with globalID could not be found in the database, when it is there ??
- Subject: Re: Object with globalID could not be found in the database, when it is there ??
- From: Owen McKerrow <email@hidden>
- Date: Wed, 28 Nov 2007 11:35:34 +1100
Hmm nope we don't have any that are cache'd in memory.
We do however have cross model relationships that involved entities
that use inheritance ( thanks for the tip Lachlan ). So I have merged
the models back into 1 ( was only for conceptual reasons they were
two) and am going to do a patch release to see if that fixes the issue.
Owen McKerrow
WebMaster, emlab
Ph : +61 02 4221 5517
http://emlab.uow.edu.au
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - -
"As of tomorrow, employees will only be able to access the building
using individual security cards. Pictures will be taken next
Wednesday employees will receive their cards in two weeks."
- "Dilbert Quotes" Winner, Fred Dales, Microsoft Corp
On 28/11/2007, at 9:53 AM, Simon McLean wrote:
Hi Xavier -
I think you might have solved our problem. We have recently
introduced JGroupSynchronizer and the entities that are affected by
the "Object with globalID could not be found" problem are indeed
flagged as "cache in memory".
Many thanks for the tip.
Simon
On 27 Nov 2007, at 14:50, Xavier Destombes wrote:
Hello Owen,
I don't know if it helps, but we got the same behavior from time
to time when we tried to both have "JGroupSynchronizer" and "cache
in memory" checked in the eomodel.
Do you have the same setup?
Xavier
Hi Anjo,
On 27/11/2007, at 6:01 PM, Anjo Krank wrote:
Am 27.11.2007 um 00:39 schrieb Owen McKerrow:
The object with globalID _EOIntegralKeyGlobalID[Person
(java.lang.Long)8917] could not be found in the database. This
could be result of a referential integrity problem with the
database. An empty fault could not be created because the
object's class could not be determined (e.g. the GID is
temporary or it is for an abstract entity).
Did you check if you *do* have this object with GID 8917 in the
prod DB?
Also, it's been a longstanding bug in WO that non-existant EOs
would get some sort of dummy-fault in some cases, leading to
erratic behaviour later on. Wonder fixed this years ago...
Cheers, Anjo
Yes that object defiantly does exist, an it sometimes does in
fact fire correctly.
Owen McKerrow
WebMaster, emlab
Ph : +61 02 4221 5517
http://emlab.uow.edu.au
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - -
'The test of a first-rate intelligence is the ability to hold
two opposed ideas in the mind at the same time and still be able
to function.'
-F.Scott Fitzgerald,
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40anazys.com
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40mac.com
This email sent to email@hidden
_______________________________________________
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