Re: jdbc Batch update stack trace - Mailing list pgsql-jdbc

From Barry Lind
Subject Re: jdbc Batch update stack trace
Date
Msg-id 3E7106FD.5070104@xythos.com
Whole thread Raw
In response to jdbc Batch update stack trace  ("Mario Rodriguez Villanea" <mrodriguez@AVANTICATEC.NET>)
List pgsql-jdbc
Mario,

In looking at the code a bit here is one thing you can look at.  The
exception you are getting back is a nested exception.  SQLException has
a getNextException() method.  If you call that on this exception you
will have the real exception that is causing the failure.

thanks,
--Barry

PS.  I will check in a fix that improves the below error message a bit.



Mario Rodriguez Villanea wrote:
> Batch entry 0 [Ljava.lang.Object;@2a6f16 was aborted.
>  at
> org.postgresql.jdbc2.AbstractJdbc2Statement.executeBatch(AbstractJdbc2St
> atement.java:105)
>  at
> com.capitales.db.common.DBConnection.getDatafromWriteBatch(DBConnection.
> java:233)
>  at
> com.capitales.db.common.DBConnection.executeComplexUpdateBatch(DBConnect
> ion.java:73)
>  at
> com.capitales.db.ecoanalisis.handlers.ImportEcoanalisis.agregarImportEco
> analisis(ImportEcoanalisis.java:169)
>  at
> com.capitales.imports.ecoanalisis.EcoanalisisProcessor.processImportData
> (EcoanalisisProcessor.java:79)
>  at
> com.capitales.imports.ecoanalisis.EcoanalisisImporter.startImportProcess
> (EcoanalisisImporter.java:83)
>  at
> com.capitales.imports.ecoanalisis.EcoanalisisImporter.startImportProcess
> (EcoanalisisImporter.java:62)
>  at com.capitales.imports.Prueba.<init>(Prueba.java:28)
>  at com.capitales.imports.Prueba.main(Prueba.java:35)
>
>
>
> ____________________________________
> Mario A. Rodríguez Villanea
> mrodriguez@avanticatec.com
> Tel Of    : 2839100
> Tel Hab : 2933432
> Avantica Technologies
> http://www.avanticatec.com <http://www.avanticatec.com/>
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>




pgsql-jdbc by date:

Previous
From: Barry Lind
Date:
Subject: Re: Batch update error
Next
From: Barry Lind
Date:
Subject: Re: changes to error reporting questions