IV96591: ALLOW THE OPTION TO TOLERATE ZERO CHANGES MADE AT THE DATABASE LEVEL ON UPDATE OPERATIONS

WebSphere Service Registry and Repository V8.5.6 Fix Pack 2

APAR status

• Closed as program error.

Error description

• The following exception is seen in the SystemOut.log when the
  Subscription Notifier runs:
  
  Sandbox       E com.ibm.sr.athene.access.Sandbox commit
  GSR5000I: Captured exception [151]:
  com.ibm.athene.exception.AtheneConcurrentModificationException:
  ATN0208E: Update failed due to concurrent updates.
  Possible instances causing failure: [URI:
  http://www.ibm.com/xmlns/prod/websphere/repository/6/3/controlOb
  ject#<bsrURI>, Version: <version>]
  
  Trace shows the following line, which suggests the exception is
  being thrown because zero changes were made as a result of the
  update:
  
  TripleStoreIm 3 com.ibm.athene.TripleStoreImpl executeBatch
  rowsChanged data for update operation, row number 0: 0
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of WebSphere Service Registry and Repository V8.5
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  If the database returns that zero changes were made, the
  subscription notifier will fail in error.
  
  This fix means that a user configurable switch can be added to
  WSRR so that zero changes are instead tolerated. Contact IBM
  Support if you believe you require this fix.
  

Problem conclusion

• This fix is targeted for inclusion in WSRR V8.5.6.2
  

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

  SERVICE REGISTR

• Fixed component ID

  5724N7200

Applicable component levels

• R850 PSY

     UP