Fixes are available
APAR status
Closed as program error.
Error description
When trying to access a CMP entity bean using the findbyprimarykey, the following exception is thrown: ---------------------------------------------------------------- javax.ejb.TransactionRolledbackLocalException: ; nested exception is: java.lang.ArrayIndexOutOfBoundsException: 0 at com.dcx.plusplus.pbl.basic.exceptions.PBL_ExceptionHelper.throwU nwrappedException(PBL_ExceptionHelper.java:131) at ... com.dcx.sqms.p75.companymasterdata.entity.websphere_deploy.DB2UD BNT_V8_1 . AddressBeanExtractor_b48044f7.extractPrimaryKey(Unknown Source) at com.ibm.ws.ejbpersistence.dataaccess.ResultCollectionImpl. processSingleRow(Unknown Source) ---------------------------------------------------------------- The problem was found to be within the EJBdeploy code generation tool. This needs to be fixed in AST v6.0, AST v6.1, WAS v6.0, and WAS v6.1.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of CMP EJBs running on WebSphere * * Application Server that make use of * * read-ahead access intents. * **************************************************************** * PROBLEM DESCRIPTION: The inclusion of read-ahead access * * intents on CMP EJBs may cause * * ArrayIndexOutOfBoundsExceptions * * during runtime. * **************************************************************** * RECOMMENDATION: * **************************************************************** The inclusion of read-ahead access intents on CMP EJBs involved in multiple relationships will cause the EJB Deploy code generation tool to produce symantically incorrect source code that can result in an ArrayIndexOutOfBoundsException when accessing the extractPrimaryKey() method of the application-specific BeanExtractor class.
Problem conclusion
The logic for parsing the JDBC indexes for the columns that are included in the read-ahead access intent has been improved to properly handle multiple CMP relationships. The fix for this APAR is scheduled for inclusion in the WebSphere Application Server v6.0.2.29 and v6.1.0.19 fix packs. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PK60611
Reported component name
WEBAPP SERVER A
Reported component ID
5724J0820
Reported release
600
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-02-07
Closed date
2008-04-08
Last modified date
2008-04-08
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
WEBAPP SERVER A
Fixed component ID
5724J0820
Applicable component levels
R600 PSY
UP
R610 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
24 October 2021