Hi Michael,
It’s an interesting problem with at first blush seems impossible but on second
pass, looks plausible.
That is clearly Wonder code so you can trace it and debug it. The line number
125 of ERXDatabaseContext.java is likely very accurate.
Stepping through (mentally) I concur that th
Heh, ya, I figured you’d say that…and who does? I’m sure someone…
If you don’t have a clue, read your SQL and find those timestamps and see what
transactions were going on.
If you can’t reproduce it, I’d guess you’ll want to turn up a bit of logging
and just do a "hunt and peck” until you see w
Jesse,
I believe we do not have any read only objects in out application…
Michael
> On Jun 26, 2020, at 12:55 PM, Jesse Tayler wrote:
>
> Well something triggered a change in a read only entity
>
> I’d guess you can see specifically by checking sql output
>
>
>> On Jun 26, 2020,
Well something triggered a change in a read only entity
I’d guess you can see specifically by checking sql output
> On Jun 26, 2020, at 12:24 PM, Michael Kondratov via Webobjects-dev
> wrote:
>
> Hello everybody!
>
>
> We started to see a strange error:
>
>
> java.lang.NullPointer
Hello everybody!
We started to see a strange error:
java.lang.NullPointerException
at
er.extensions.eof.ERXDatabaseContext._verifyNoChangesToReadonlyEntity(ERXDatabaseContext.java:125)
at
com.webobjects.eoaccess.EODatabaseContext.performChanges(EODatabaseContext.java:6
