Fixes are available
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
APAR status
Closed as program error.
Error description
In Websphere Application Server v7.0.0.x, the following warning messages are logged in the SystemOut.log though the "RESTRICT LONG RUNNING LOCKS" feature is not enabled on the Service Integration Bus messaging engine: SibMessage W [XXX_bus:XYZ_Cluster.000-XXX_bus] Restrict DB locking feature cannot be enabled, since Messaging Engine is trying to connect to the datastore that is incompatible or not supported with this version of WAS .
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of the default messaging provider for * * IBM WebSphere Application Server * **************************************************************** * PROBLEM DESCRIPTION: When "Restrict long running locks" * * feature is not enabled for a messaging * * engine then the CWSIS1602W message * * should * * not be logged in the SystemOut.log * * files. * **************************************************************** * RECOMMENDATION: None * **************************************************************** When "Restrict long running locks" feature is not enabled for a messaging engine then the below message should not be logged in the SystemOut.log files. [5/22/14 17:01:36:803 CEST] 00000011 SibMessage W [itim_bus:ITIM_Messaging_Cluster.000-itim_bus] CWSIS1602W: Restrict DB locking feature cannot be enabled, since Messaging Engine is trying to connect to the datastore that is incompatible or not supported with this version of WAS However the message is observed in the SystemOut.log files even when the feature is not enabled.
Problem conclusion
The message is conveying the information that the sibDBUpgrade script is not run on the SIB tables. The "Restrict long running locks" feature requires some schema changes to the SIB tables. This script performs these changes. While starting, the messaging engine can detect if the feature is enabled and the required changes are not made to SIB tables through the script. If it is the case, the feature is disabled and default behaviour to use the long running locks is applied. The fix for this APAR is currently targeted for inclusion in fix packs 7.0.0.37, 8.0.0.10, 8.5.5.4. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PI19322
Reported component name
WAS SIB & SIBWS
Reported component ID
620800101
Reported release
300
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-06-04
Closed date
2014-09-09
Last modified date
2015-01-15
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
WAS SIB & SIBWS
Fixed component ID
620800101
Applicable component levels
R800 PSY
UP
R850 PSY
UP
Document Information
Modified date:
28 April 2022