Are you using change notification? I have seen the #3 problem you
describe if you add attributes to a change-notified entity and don't
roll all cooperating instances at the same time.
(ie, an instance which doesn't know about a new attribute posts a
change snapshot to an instance which does, and the instance that does
know about the attribute throws the exception because the snapshot
which it recorded in response to the notification lacks the new
attribute.)
On Jul 12, 2006, at 12:58 PM, David Sargent wrote:
Recently I started getting errors dealing with snapshots. I don’t
know if they are related or not. The errors are:
1) There is no database snapshot available for the object.
2) Exception occurred while handling request:
java.lang.IllegalStateException: incrementSnapshotCountForGlobalID:
com.webobjects.eoaccess.EODatabase
[EMAIL PROTECTED] -- is unable to increment
snapshot count for object with global ID _EOIntegralKeyGlobalID
[Merchant (java.lang.Integer)2906] - no snapshot exists
3) _databaseOperator = "EODatabaseUpdateOperator"; } does not
contain value for attribute named assignUserRID with snapshot key:
assignUserRID
I can not reproduce the problem. It appears to happen randomly( I
know that something is triggering it). From what I can see, it
triggers during the save of the session default EC. The nested EC
is saving fine.
I was under the impressing that snapshots where handled by EOF and
I did not need to deal with them. So something I am doing must be
bothering them.
I am lost as to where to look. I have put in debug code to try to
narrow it down more. Any suggestions or directions would be
appreciated. Has anyone else seen these kind of errors.
Thanks
David
--
WireHose: Smart metadata and personalization for WebObjects.
http://www.wirehose.com/
_______________________________________________
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]
