Subject | Error in JayBird 1.0.1 ? |
---|---|
Author | Steffen Heil |
Post date | 2004-06-04T16:20:51Z |
Hi
I keep getting this (occasionally, not alway):
java.lang.ArrayIndexOutOfBoundsException: 2
at org.firebirdsql.jgds.GDS_Impl.isc_vax_integer(GDS_Impl.java:1300)
at
org.firebirdsql.jgds.GDS_Impl.parseTruncSqlInfo(GDS_Impl.java:1901)
at org.firebirdsql.jgds.GDS_Impl.parseSqlInfo(GDS_Impl.java:1873)
at
org.firebirdsql.jgds.GDS_Impl.isc_dsql_prepare(GDS_Impl.java:1163)
at
org.firebirdsql.jca.FBManagedConnection.prepareSQL(FBManagedConnection.java:
767)
at
org.firebirdsql.jdbc.FBConnection.prepareSQL(FBConnection.java:1107)
at
org.firebirdsql.jdbc.FBStatement.prepareFixedStatement(FBStatement.java:942)
at
org.firebirdsql.jdbc.FBPreparedStatement.prepareFixedStatement(FBPreparedSta
tement.java:699)
at
org.firebirdsql.jdbc.FBPreparedStatement.<init>(FBPreparedStatement.java:78)
at
org.firebirdsql.jdbc.FBConnection.prepareStatement(FBConnection.java:243)
But I cannot track it down to a special case, since this only occurs in our
servlets an I have no way to debug them in production.
What can I do to track this down?
Regards,
Steffen
I keep getting this (occasionally, not alway):
java.lang.ArrayIndexOutOfBoundsException: 2
at org.firebirdsql.jgds.GDS_Impl.isc_vax_integer(GDS_Impl.java:1300)
at
org.firebirdsql.jgds.GDS_Impl.parseTruncSqlInfo(GDS_Impl.java:1901)
at org.firebirdsql.jgds.GDS_Impl.parseSqlInfo(GDS_Impl.java:1873)
at
org.firebirdsql.jgds.GDS_Impl.isc_dsql_prepare(GDS_Impl.java:1163)
at
org.firebirdsql.jca.FBManagedConnection.prepareSQL(FBManagedConnection.java:
767)
at
org.firebirdsql.jdbc.FBConnection.prepareSQL(FBConnection.java:1107)
at
org.firebirdsql.jdbc.FBStatement.prepareFixedStatement(FBStatement.java:942)
at
org.firebirdsql.jdbc.FBPreparedStatement.prepareFixedStatement(FBPreparedSta
tement.java:699)
at
org.firebirdsql.jdbc.FBPreparedStatement.<init>(FBPreparedStatement.java:78)
at
org.firebirdsql.jdbc.FBConnection.prepareStatement(FBConnection.java:243)
But I cannot track it down to a special case, since this only occurs in our
servlets an I have no way to debug them in production.
What can I do to track this down?
Regards,
Steffen