Re: NullPointerException only after first call to batchFetchRelationship
Kaj Hejer <[email protected]> Tue, 13 Jan 2004 14:25:55 +0100
| Newsgroups | gmane.comp.web.webobjects.eof |
|---|---|
| Message-ID | <p0602046dbc29a10c7868@[10.29.0.60]> |
At 11:00 -0800 15-12-03, Chuck Hill wrote:
>I also do a lot of batchFetchRelationship and have not seen this.
>Yet. We don't often use child EC's so that may explain it.
>
>Strange, hard to reproduce, errors like this can be the result of an
>editing context processing notifications sent by another editing
>context. Tracking this down can be very difficult. I looked at the
>stack trace that Kaj posted but did not see any evidence of this.
>It looks like something in EODatabaseContext is hosed.
>
Hi!
Just fyi I now get the
[2004-01-13 13:51:24 MET] <WorkerThread6> java.lang.NullPointerException
at
com.webobjects.eocontrol._EOMutableKnownKeyDictionary.<init>(_EOMutableKnownKeyDictionary.java:90)
at
com.webobjects.eoaccess.EORelationship._foreignKeyForSourceRow(EORelationship.java:1094)
stacktrace when I don't use batchFetchRelationship.
We use prefetching in the fetch where I get this exception.
The ec here is session.defaultEditingContext.
See full stacktrace at http://folk.uio.no/kajh/tmp/wo20040113.txt
-Kaj :)