When the java.lang.ArrayIndexOutOfBoundsException is seen on top of of JCC stack, one of potential causes could be application design issue.
Example of affected JCC stack:
Caused by: java.lang.ArrayIndexOutOfBoundsException
Note that as the JCC driver code is obfuscated, the stack may be different with different JCC driver versions.
The JCC JDBC driver caches cursors associated with prepared statements for future reuse for performance reasons. There is however a tradeoff - a cursor description is not parsed again when a cursor is cached. Hence when underlying DDL of a table changes, the cursor definition may no longer be valid. An application programmer needs to verify that the DDL does not change inbetween subsequent cursor invocations.
Diagnosing the problem
De-obfuscated stack should show that ArrayIndexOutOfBoundsException is raised by T4Cursor.readFdocaOneByte method.
Resolving the problem
Redesign an application or set the useCachedCursor JCC property to false (the default is true )