The OpenJPA StoreException class has a "type" property that may provide you additional information. Make sure also that you're printing out the stack trace of the nested exception.
Check out the JavaDoc for the exception class: http://openjpa.apache.org/builds/1.2.0/apache-openjpa-1.2.0/docs/javadoc/index.html -Tim On Mon, 2009-02-23 at 15:28 -0800, kurt_cobain wrote: > The problem is that it isn't telling me "why" the transaction has been rolled > back; for example the way you do if you try and insert a null value into a > non-nullable column etc, you typically get a jdbc error. I'm getting zero... > > > > > ________________________________ > From: Pid (via Nabble) <ml-user+185223-1141408...@n2.nabble.com> > To: kurt_cobain <tracyjmilb...@yahoo.com> > Sent: Monday, February 23, 2009 5:23:40 PM > Subject: Re: How to get beter stacktraces???? > > kurt_cobain wrote: > > > I'm having a very difficult time with OpenJPA (via weblogic). > > > > I often get a strack trace that doesn't help me at all, it just looks like > > this: > > > > "org.apache.openjpa.util.StoreException: The transaction has been rolled > > back. See the nested exceptions for details on the errors that occurred." > > > > And yet, there ARE no more details on the error. I've been able to figure > > out a couple of the issues by basically feeling around in the dark and > > guessing, but is there ANY way to get better error messages than that? > > > > Please advise... > You could add debugging messages to the source code & recompile it. > Of course, you might be better off asking on the OpenJPA list... > > p > > > > > > ________________________________ > > This email is a reply to your post @ > http://n2.nabble.com/How-to-get-beter-stacktraces-----tp2375022p2375045.html > You can reply by email or by visting the link above. > > >
