PK53402: AIOOB EXCEPTION AFTER UPGRADE OF OJDBC14.JAR FILE. JAVA.LANG.ARRAYINDEXOUTOFBOUNDSEXCEPTION

APAR status

• Closed as program error.

Error description

• AIOOB exception after upgrade of OJDBC14.jar file.
  java.lang.ArrayIndexOutOfBoundsException: 2770468
   at oracle.jdbc.driver.T4CPreparedStatement.doOall8
                      (T4CPreparedStatement.java(Compiled Code))
   at oracle.jdbc.driver.T4CPreparedStatement.fetch
                      (T4CPreparedStatement.java:1038)
   at oracle.jdbc.driver.OracleResultSetImpl.
      close_or_fetch_from_next(OracleResultSetImpl.java:291)
   at oracle.jdbc.driver.OracleResultSetImpl.next
                      (OracleResultSetImpl.java(Compiled Code))
   at GetIVSOrgCode3.executeSQL
                      (GetIVSOrgCode3.java(Compiled Code))
   at GetIVSOrgCode3.main(GetIVSOrgCode3.java:77)
  
  Problem occurs on LinuxIA32/Windows/zLinux/zOS.
  
  Problem cause : The problem is caused when JIT compilation of
  methods results in a memop being generated for the first
  argument to size verification quads. This cannot be specifically
  made out from the external JAVA code. The problem is because the
  optimizer if free to tag either of the sources to quads as a
  memory operand, but the code generator expects that first
  argument be a non-memory operand.
  

Local fix

• Workaround :
  JITC_COMPILEOPT=NQUD_DU
  or
  JITC_COMPILEOPT=COMPILING:SKIP{oracle/jdbc/driver/T4CPreparedSta
  tement}{doOall8}
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: IBM WebSphere Application Server version     *
  *                 6.0.2 users                                  *
  ****************************************************************
  * PROBLEM DESCRIPTION: AIOOB exception after upgrade of        *
  *                      OJDBC14.jar file                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The problem is caused when JIT compilation results in a memop
  being generated for the first argument to size verification
  quads. This cannot be specifically made out from the external
  JAVA code. The problem is because the optimizer if free to tag
  either of the sources to quads as a memory operand but the
  code generator expects that first argument be a non-memory
  operand.
  

Problem conclusion

• Devised the code to specifically check that if under certain
  circumstances we arrive at a conclusion that a particular
  operand be tagged as a memory operand for certain quadruple
  then verify that the codegen respects this. If not then do
  not classify the operand as a memory based operand.
  

Temporary fix

• JTC_COMPILEOPT=NQUD_DU
  

Comments

APAR Information

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

  PK53307

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

Modules/Macros

• SDK
  

Fix information

• Fixed component name

  WEBSPH APP SERV

• Fixed component ID

  5724J0800

Applicable component levels

• R60A PSY

     UP

• R60H PSY

     UP

• R60I PSY

     UP

• R60S PSY

     UP

• R60W PSY

     UP

• R60Z PSY

     UP