Re: [eclipselink-users] EclipseLink dropping Exception cause?
I tracked this down to DatabaseAccessor.java:1340.
It looks like
org.apache.derby.impl.jdbc.EmbedConnection40.prepareStatement() throws a
NullPointerException without a stack-trace and to make it even more
colorful, "cause" points back to the wrapping exception.
In short, Derby is messed up ;) This makes little sense, however, because it
turns out that derby.log contains the full stack-trace. I wonder why the
EmbeddedConnection driver throws a bogus exception even if it logs the
correct one in its own logs.
Thanks anyway ;)
Tim Hollosy wrote:
> Have you tried running in debug mode and setting a breakpoint in the
> eclipselink source?
> On Sat, Sep 27, 2008 at 9:51 PM, cowwoc <cowwoc@xxxxxxxxxxxxxxxx> wrote:
>> I used Proguard to removed unused classes, too many in fact, and now I
>> the following exception:
>> [EL Warning]: 2008.09.27
>> [EclipseLink-4002] (Eclipse Persistence Services - 1.0.1 (Build
>> org.eclipse.persistence.exceptions.DatabaseException Internal Exception:
>> java.sql.SQLException: Java exception: ':
>> Error Code: 0
>> I'm wondering why SQLException is missing a "cause". Did EclipseLink drop
>> or did Derby? I absolutely need the cause in order to figure out what
>> needs to be kept.
>> Thank you,
>> View this message in context:
>> Sent from the EclipseLink - Users mailing list archive at Nabble.com.
>> eclipselink-users mailing list
> eclipselink-users mailing list
View this message in context: http://www.nabble.com/EclipseLink-dropping-Exception-cause--tp19708124p19718084.html
Sent from the EclipseLink - Users mailing list archive at Nabble.com.