PH25449: OPTIMISTIC LOCK ERROR OCCURS DURING RECONCILIATION OF INBOUND DUPLICATE 997 DOCUMENTS

APAR status

• Closed as program error.

Error description

• Enveloping data using the SPEEnvelope service from a
  Sterling B2B Integrator Business Process results in an error of:
  
  [SPEDeenveloping] processData: log contents: Resource XXXXXX:
  Optimistic locking errors were detected when flushing to the
  data store. The following objects may have been concurrently
  modified in another transaction:
  [com.ibm.spe.core.docstate.DocumentState-128530161g55cg488node1|
  GS GE]
  

Local fix

• ITXA Github: 78
  TR / TR
  Circumvention: None
  

Problem summary

• Problem Description: Issue #78, TS003692336: Intermittent
  OptimisticLockException reconciling 997 documents.
  

Problem conclusion

• Problem Conclusion: OptimisticLockExceptions were found several
  years ago and a property was originally put in place to control
  synchronous access to the state record:
  
  spe.ReconcileACK_sync=true
  
  The implementation to support this property was incomplete. The
  property activates use of a mutex for controlling the update of
  the document state record. However, this mutex did not prevent
  other nodes in the cluster from attempting to update the same
  document state record.
  
  To address this issue, a cluster-wide lock is needed using
  JGroups. The identifier for lock needs to be the document ID.
  
  Platforms Affected: All
  Customers Affected: Customers performing simultaneous enveloping
  and reconcile operations.
  Applies to: SPE.COMMON.9.0.2.1, SPE.COMMON.10.0.1.1
  

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:

Fix information

• Fixed component name

  ITX ADV

• Fixed component ID

  5724Q2301

Applicable component levels