JR36981: java.lang.IndexOutOfBoundsException, error when using Salesforce Pack 1.5 with reject link and Bulk Load

APAR status

• Closed as program error.

Error description

• when using Salesforce pack 15 release and IS 81, with reject
  link enabled and running in bulk loading mode, job sometimes
  will abort with java.lang.IndexOutOfBoundsException: Index:
  23, Size: 2, at java.util.LinkedList.entry (LinkedList.java:
  383)
  at java.util.LinkedList.get (LinkedList.java: 328)
  at
  com.ibm.is.erp.salesforce.jcconnector.CC_SALESFORCEJCRejectData
  SetProducer.processOneTopLevelDataItem
  (CC_SALESFORCEJCRejectDataSetProducer.java: 282)
  at
  com.ascential.e2.connector.CC_RecordDataSetProducer.produceOneT
  opLevelDataItem
  

Local fix

• we have an error in the code need to reset the tracking index
  to 0 when there's no more error text returned.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  user using salesforce connector 15 release or 81
  ****************************************************************
  PROBLEM DESCRIPTION:
  when user is using bulk loading mode on 81 with salesforce pack
  15 and with reject link enabled, sometimes, user will
  encountered the follow run time exception :
  SFC_Account,4: java.lang.IndexOutOfBoundsException: Index: 23,
  Size: 2
  at java.util.LinkedList.entry (LinkedList.java: 383)
  at java.util.LinkedList.get (LinkedList.java: 328)
  at
  com.ibm.is.erp.salesforce.jcconnector.CC_SALESFORCEJCRejectDataS
  etProducer.processOneTopLevelDataItem
  (CC_SALESFORCEJCRejectDataSetProducer.java: 274)
  at
  com.ascential.e2.connector.CC_RecordDataSetProducer.produceOneTo
  pLevelDataItem (CC_RecordDataSetProducer.java: 208)
  at com.ascential.e2.daapi.CC_RejectManager.reportRejectRecord
  (CC_RejectManager.java)
  at
  com.ibm.is.erp.salesforce.jcconnector.CC_SALESFORCEJCRecordDataS
  etConsumer.checkRestApiStatus
  (CC_SALESFORCEJCRecordDataSetConsumer.java: 2159)
  ****************************************************************
  RECOMMENDATION:
  we'll build a patch for all the issues discovered post GA.
  Patch number probably will be using JR36952
  ****************************************************************
  

Problem conclusion

• issue was resolved when reset a index counter to 0 when there's
  no more error text.
  

Temporary fix

Comments

APAR Information

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

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

Modules/Macros

• 810N
  

Fix information

• Fixed component name

  WIS DATASTAGE

• Fixed component ID

  5724Q36DS

Applicable component levels

• R810 PSN

     UP