|
Problem IT37126
|
Status: Closed |
ARRAYINDEXOUTOFBOUNDSEXCEPTION OCCURS DURING MULTITHREADED SQLJ APPLICATION PROFILE PROCESSING.
|
| product: |
DB2 CONNECT / DB2CONNCT / B50 - DB2 |
| Problem description: |
When a multi-threaded SQLJ application accessing multiple
profiles is executed, the application may hit
ArrayIndexOutOfBoundsException for profile access due to an
invalid index being returned by SQLJ
runtime and the same is passed by application.
This problem might occur due to concurrent access to profile
group that is shared across the application by multiple threads
and due to non-serialized access to operations manipulating the
profiles index.
stack trace that can be seen is:
[sqlj][time:2021-05-25-10:37:43.927][Thread:WebSphere non-WLM
Dispatch Thread t=xxxxxxxxx]SQLJFataError:
ConnectedGroup.getProfile() for key 1 is called - but number of
connectedProfiles are 1
[sqlj][time:2021-05-25-10:37:43.928][Thread:WebSphere non-WLM
Dispatch Thread
t=xxxxxxxxx]SQLJFatalError:StackTrace:java.lang.ArrayIndexOutOfB
oundsException: 1 >= 1
java.util.Vector.elementAt(Vector.java:486)
sqlj.runtime.ref.ProfileGroup$ConnectedGroup.getProfile(ProfileG
roup.java:468)
sqlj.runtime.ref.ConnectionContextImpl.getConnectedProfile(Conne
ctionContextImpl.java:285)
sqlj.runtime.ExecutionContext.registerStatement(ExecutionContext
.java:677) |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* DB2 SQLJ users *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to V11.5.7.0 or later *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* DB2 SQLJ users *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to V11.5.7.0 or later *
**************************************************************** |
| Comment |
Problem fixed in Db2 Version V11.5.7.0(JCC version 4.31.x) |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 04.06.2021
13.10.2021
13.10.2021 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
