PM30754: INCORRECT ARRAYINDEXOUTOFBOUNDSEXCEPTION FROM COMPILED CODE.

APAR status

• Closed as program error.

Error description

• Error Message: When used the DB2 JDBC driver version 3.61,
  ArrayIndexOutOfBoundsException was seen to be thrown from the
  compiled code.
  .
  Stack Trace: java.lang.ArrayIndexOutOfBoundsException
  
  at com.ibm.db2.jcc.t4.cb.a(cb.java(Compiled Code))
  
  at com.ibm.db2.jcc.t4.cb.a(cb.java:1886)
  
  at com.ibm.db2.jcc.t4.cb.m(cb.java:726)
  
  at com.ibm.db2.jcc.t4.cb.i(cb.java:246)
  
  at com.ibm.db2.jcc.t4.cb.c(cb.java:54)
  
  at com.ibm.db2.jcc.t4.q.c(q.java:44)
  
  at com.ibm.db2.jcc.t4.rb.j(rb.java:147)
  
  at com.ibm.db2.jcc.am.bn.ib(bn.java:2048)
  
  at com.ibm.db2.jcc.am.cn.b(cn.java:3855)
  
  at com.ibm.db2.jcc.am.cn.cc(cn.java:678)
  
  at com.ibm.db2.jcc.t4.l.cc(l.java:115)
  
  at com.ibm.db2.jcc.am.cn.executeQuery(cn.java:652)
  ...
  .
  None.
  

Local fix

• JITC_COMPILEOPT="COMPILING(SIGNATURE):SKIP{com/ibm/db2/jcc/t4/cb
  }{a(Lcom/ibm/db2/jcc/t4/d;ZZ)V}"
  

Problem summary

• The problem was due to a bad array bounds related optimization
  in the JIT compiler which incorrectly checks the arraylength
  againsst itself, and throws the bounds exception in case found
  to be equal or more.
  

Problem conclusion

• This defect will be fixed in:
  1.4.2 SR13 FP9
  .
  The incorrect behavior of array bounds check optimization
  is fixed and the array bounds are now correctly checked.
  .
  To obtain the fix:
  Install build 20110202 or later
  

Temporary fix

• Use the following JIT compiler option:
  
  JITC_COMPILEOPT="SKIP{com/ibm/db2/jcc/t4/cb}{a(Lcom/ibm/db2/jcc/
  t4/d;ZZ)V}
  

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  JAVA(1.3/1.4 CO

• Fixed component ID

  5648C9800

Applicable component levels

• R14A PSY

     UP