It will omit the trace if it has happened a very large number of times. If you restart the server it will start printing it again when it happens.
On Fri, May 7, 2021 at 7:26 AM Hugi Thordarson <h...@karlmenn.is> wrote: > One would think so, but there's just no stack trace printed for the > NullPointerException. > > > > On 7 May 2021, at 12:24, John Huss <johnth...@gmail.com> wrote: > > > > The first line of the stack after the Caused By line would tell you the > > line with the problem, wouldn't it? What was that line? > > > > On Fri, May 7, 2021 at 7:16 AM Hugi Thordarson <h...@karlmenn.is> wrote: > > > >> Hi all, > >> > >> occasionally my users encounter errors when committing changes to the > DB. > >> The relevant part of the stack trace looks like this: > >> > >> --------- > >> org.apache.cayenne.CayenneRuntimeException: [v.4.1 Jul 14 2020 10:26:08] > >> Commit Exception > >> at > >> > org.apache.cayenne.access.DataContext.flushToParent(DataContext.java:774) > >> at > >> > org.apache.cayenne.access.DataContext.commitChanges(DataContext.java:691) > >> [...removed rest of trace…] > >> Caused by: java.lang.NullPointerException > >> --------- > >> > >> Unfortunately I've been unable to reproduce this error, so before I dive > >> into it I'm wondering if this looks familiar to anyone, if there are > >> obvious places to look or if there are recommendations for strategies to > >> debug? > >> > >> Cheers, > >> - hugi > >
