Menu

#343 Descriptor index not valid while querying metadata in v7r1

JDBC
closed-rejected
None
5
2014-07-22
2013-01-11
Josh
No

All of our v7r1 customers are hitting this issue sporadically but the error does not happen in v6r1 or earlier. It appears in both versions of jtopen we have in use (5.4 and 7.2). Everything seems ok at first but over weeks and months we hit this more and more often. We suspect we're hitting some kind of system limits either in the jtopen driver or on the server side.

The only workaround we have found so far that works is to use the jdbc connection property "metadata source=0". We've been unable to determine if this is a JTOpen issue, a server issue, or an issue with our code. We're hoping you can advise us.

sqlstate=07009, code=-99999

java.sql.SQLException: Descriptor index not valid. (class java.lang.ArrayIndexOutOfBoundsException)
at com.ibm.as400.access.JDError.throwSQLException(JDError.java:521)
at com.ibm.as400.access.JDError.throwSQLException(JDError.java:418)
at com.ibm.as400.access.JDServerRow.getSQLData(JDServerRow.java:412)
at com.ibm.as400.access.JDSimpleRowCache.<init>(JDSimpleRowCache.java:129)
at com.ibm.as400.access.AS400JDBCDatabaseMetaData.getPrimaryKeys(AS400JDBCDatabaseMetaData.java:2910)

Discussion

  • John Eberhard

    John Eberhard - 2013-08-13

    Is it possible to get a JDBC and datastream trace of the failing scenario?

     
  • John Eberhard

    John Eberhard - 2013-08-13
    • assigned_to: John Eberhard
     
  • John Eberhard

    John Eberhard - 2014-07-22
    • status: open --> closed-rejected
     
  • John Eberhard

    John Eberhard - 2014-07-22

    Closing. Requested information not provided.

     

Log in to post a comment.

MongoDB Logo MongoDB