Fixes are available
APAR status
Closed as program error.
Error description
Depending on the application design and various settings the transaction may not be set to rollback when a runtime exception is received by an SCA binding. More detailed SCA transaction product behavior can be found here: http://pic.dhe.ibm.com/infocenter/wasinfo/v7r0/topic/com.ibm.web sphere.soafep.multiplatform.doc/info/ae/ae/csca_global_trans.htm l If a global transaction is owned by another component other than SCA then that component's behavior can also affect the global transation. Beginning in WAS and WPS v7, the SCA transaction handling behavior did change from always forcing a rollback in a global transaction to only forcing a rollback when SCA completes the global transaction with an unchecked exception. This APAR is to provide a configurable flag to get the old behavior. You can enable this WebSphere Process Server V6.x transaction behavior by creating the SCA_ROLLBACK_TRANSACTION_IMPORT WebSphere environment variable and setting its value to true once the APAR is applied. With this flag, when a JAX-RPC import is called with join transaction to true and the web service provider responds with a unmodeled business fault there will be a ServiceRuntimeException and the binding will mark the transaction for rollback only. With the default WPS 7 and above scenario, the import would still throw the ServiceRuntimeException but it would only mark the transaction to rollback if the exception is not caught by the time it reaches an SCA method or binding which started the global transaction.
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: IBM Business Process Manager (BPM) * * Advanced users * **************************************************************** * PROBLEM DESCRIPTION: The global transaction may not be set * * to rollback when a runtime exception * * is received by an SCA binding. * **************************************************************** * RECOMMENDATION: * **************************************************************** There is a design change for SCA-related global transactions when join transaction is set to true in WebSphere Server V6.x versions. The import binding marks the global transaction to be rolled back and throws a runtime exception. In WebSphere Process Server V7 and later versions and IBM BPM Advanced, the import binding does not mark the transaction to be rolled back, but the user receives the Service Runtime exception to decide what to do: use the old or new behavior.
Problem conclusion
The fix provides a configurable flag for the consumer to get the oldproduct behavior. Apply the interim fix from Fix Central. Then see the installation and dependency information in the readme.txt file, which is available with the fix package as a separate download.
Temporary fix
Comments
APAR Information
APAR number
JR47431
Reported component name
BPM ADVANCED
Reported component ID
5725C9400
Reported release
801
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-08-06
Closed date
2013-10-29
Last modified date
2013-11-06
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 ADVANCED
Fixed component ID
5725C9400
Applicable component levels
R750 PSY
UP
R800 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSFTN5","label":"IBM Business Process Manager Advanced"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.1","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
07 January 2022