openjpa-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiran Chaudhuri" <>
Subject Re: How to find cause for PersistenceException?
Date Wed, 09 Jul 2008 06:25:01 GMT
Hi, Pinaki.

Even the full stack trace had no reference to the field that was accessed at 
that time.
Unfortunately right now I do not see how to reproduce that stack trace. The 
cause is that I played around with many things and finally let Netbeans 
generate my entities again, seeing that all CHAR(1) columns now map to 

Thank you for your interest. If the problem shows up again I will come back 
and post a full stack trace.


----- Original Message ----- 
From: "Pinaki Poddar" <>
To: <>
Sent: Monday, July 07, 2008 3:50 PM
Subject: Re: How to find cause for PersistenceException?

Please post the entire stack trace.
PersistenceException often nests the root cause of the error and your
application needs to recurse through those nested exception to pick the root
In this case, the context where the error has been detected is likely to be
too narrow to provide enough information (whereas in most cases, OpenJPA
exception provides adequate contextual information) -- but having the entire
stack trace will help.

Hiran Chaudhuri wrote:
> Hi there.
> On classes generated from a database with Netbeans 6.1 I get such an
> exception at runtime:
> <openjpa-1.1.0-r422266:657916 nonfatal general error>
> org.apache.openjpa.persistence.PersistenceException: Invalid value for
> getInt() - 'N'
> Now I can imagine that int is a wrong mapping for the regarding table
> column and I know which table is accessed - but how do I find out which
> column this message relates to?
> Hiran Chaudhuri
> _______________________________________________________________________
> Jetzt neu! Sch├╝tzen Sie Ihren PC mit McAfee und WEB.DE. 30 Tage
> kostenlos testen.

View this message in context:
Sent from the OpenJPA Users mailing list archive at

View raw message