JR59098: IF YOU REUSE A FAULT MESSAGE FOR MULTIPLE OPERATIONS IN A WSDL FILE, YOU RECEIVE A SQLINTEGRITYCONSTRAINTVIOLATIONEXCEPTION

8.6.0.0-WS-BPM-IFJR59098
8.6.0.201712-WS-BPM-IFJR59098
bpm.8600.cf2018.03.delta.repository

APAR status

• Closed as program error.

Error description

• When multiple operations are declared in your WSDL file and some
  or all of the operations have a fault defined with a reused
  fault message, the first discovery and the creation of an
  associated external service for this WSDL file succeed in the
  web IBM Process Designer without an error. However, if you
  rediscover this WSDL file and specify to replace the existing
  external service, the rediscovery fails with the following
  SQLIntegrityConstraintViolation exception:
  
  Error
  The software application has generated an error. Contact your
  system administrator for assistance.
  Details: Unable to load
  https://stick:9443/rest/bpm/wle/pd/v1/asset?containerRef=2063.d3
  67c75b-45ea-4dcf-a483-547ad03d6dcb&avoidBasicAuthChallenge=true
  status: 500
  
  In the  SystemOut.log file you see one of the following errors:
  
  If your database management system is Oracle:
  java.sql.SQLIntegrityConstraintViolationException: ORA-00001:
  unique constraint (POC_DEV_BPM_PSS.LSWC_PO_VERSIONS) violated
  
  If your database management system is IBM DB2:
  Error for batch element #1: DB2 SQL Error: SQLCODE=-803,
  SQLSTATE=23505, SQLERRMC=1;DB2ADMIN.LSW_PO_VERSIONS,
  DRIVER=4.21.29; nested exception is
  com.ibm.db2.jcc.am.SqlIntegrityConstraintViolationException:
  Error for batch element #1: DB2 SQL Error: SQLCODE=-803,
  SQLSTATE=23505, SQLERRMC=1;DB2ADMIN.LSW_PO_VERSIONS,
  DRIVER=4.21.29
  at
  org.springframework.jdbc.support.SQLErrorCodeSQLExceptionTransla
  tor.doTranslate(SQLErrorCodeSQLExceptionTranslator.java:239)
  at
  org.springframework.jdbc.support.AbstractFallbackSQLExceptionTra
  nslator.translate(AbstractFallbackSQLExceptionTranslator.java:73
  )
  
  PRODUCTS AFFECTED
  IBM Business Process Manager (BPM)
  IBM BPM Express
  

Local fix

• Instead of replacing the existing external service, create a new
   external service and then remove the references to the old
  external service to use the new external service.
  

Problem summary

• During discovery, the fault messages are not recognized as a
  single shared message. Instead, they are considered independent
  objects.
  Although the subsequent database operation can create the first
  object, the second creation fails because the keys for both
  objects are the same and the first one can't be overwritten.
  

Problem conclusion

• A fix that enables the discovery code to handle shared fault
  messages correctly will be available in a future release of IBM
  BPM.
  

Temporary fix

• Instead of replacing the existing external service, create a new
   external service and then remove the references to the old
  external service to use the new external service.
  

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

  BPM

• Fixed component ID

  5737A5700

Applicable component levels