Fixes are available
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
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
Failing scenarios: WLM Returned to null / FAILED for the following requests: 1) All requests coming with name=sca/sk.vub.esb.DocMgmtAndArch, type=WSAF_SIB_DESTINATION are failing. (Having said this, this destination exists in this bus) - Need to confirm is this valid request ??? 2) Failed due to mismatch of --> name=lobjmeOCluster, type=WSAF_SIB_BUSMEMBER *************************************************************** 11/7/18 13:46:23:283 CET] 00000001 NoAvailableTa > <init> Entry com.ibm.ws.cluster.selection.SelectionCriteriaImpl@95956de1[{bus =BPM.LOBJO.Bus, name=lobjmeOCluster, type=WSAF_SIB_BUSMEMBER}:{AcceptableStates=[B@2c823b1a, rules.precedence=[Lcom.ibm.wsspi.cluster.selection.SelectionRule ;@6b91ac60}] [11/7/18 16:23:30:563 CET] 00000177 NoAvailableTa > <init> Entry com.ibm.ws.cluster.selection.SelectionCriteriaImpl@62baebe1[{bus =BPM.LOBJO.Bus, name=sca/sk.vub.esb.DocMgmtAndArch, type=WSAF_SIB_DESTINATION}:{AcceptableStates=[B@a457e0cd, rules.precedence=[Lcom.ibm.wsspi.cluster.selection.SelectionRule ;@df8752de}] [11/7/18 16:30:07:346 CET] 000001b4 NoAvailableTa > <init> Entry com.ibm.ws.cluster.selection.SelectionCriteriaImpl@62baebe1[{bus =BPM.LOBJO.Bus, name=sca/sk.vub.esb.DocMgmtAndArch, type=WSAF_SIB_DESTINATION}:{AcceptableStates=[B@a457e0cd, rules.precedence=[Lcom.ibm.wsspi.cluster.selection.SelectionRule ;@df8752de}] *************************************************************** It looks like the scenario that causes the problem is this. 1)The Messaging Engine is running using queue=xxx uuid=1234. 2)The DManager loads a definition of queue=xxx uuid=5678. This is effectively a deletion of the old queue followed by an addition of the new one, except that the Messaging Engine was not told about the deletion, just that the new queue exists. 3) The Messaging Engine deletes queue=xxx uuid=1234,and the Put and Get capabilities from the Workload Manager. 4) The Messaging Engine removes the QueueName name from the Workload Manager. 5) The Messaging Engine then creates queue=xxx uuid=5678 and adds the Put and Get capabilities to the Workload Manager. 6) The Messaging Engine adds its name to the Workload Manager. The bug is that step 6) overtakes step 4) so we end up with the Put and Get capabilities but no queueName in the workload manager, hence select fails.
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server * **************************************************************** * PROBLEM DESCRIPTION: CWSIT0019E: No suitable messaging * * engine is available on bus. * * The issue is sometimes encountered * * after a BPM deploy. * **************************************************************** * RECOMMENDATION: Apply the Apar fix. * **************************************************************** No suitable messaging engine is available is reported even though the configuration is correct and a suitable messaging engine is available. This problem manifests itself as: CWSIT0019E: No suitable messaging engine is available on bus The scenario that causes the problem is: 1)The Messaging Engine is running using queue=xxx uuid=1234. 2)The DManager loads a definition of queue=xxx uuid=5678 without having deleted the uuid=1234 queue. This is effectively a deletion of the old queue followed by an addition of the new one, except that the Messaging Engine was not told about the deletion, just that the new queue exists. 3) The Messaging Engine deletes queue=xxx uuid=1234,and the Put and Get capabilities from the Workload Manager. 4) The Messaging Engine removes the QueueName name from the Workload Manager. 5) The Messaging Engine then creates queue=xxx uuid=5678 and adds the Put and Get capabilities to the Workload Manager. 6) The Messaging Engine adds its name to the Workload Manager. The error condition occurs when step 6) is performed before step 4) resulting in the Put and Get capabilities but no queueName in the workload manager, resulting in failure of the select.
Problem conclusion
The code was modified so that the new WLM entry for the destination is added after the existing one is removed. The fix for this APAR is currently targeted for inclusion in fix packs 8.5.5.15, 9.0.0.11 Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Update the description of the affected queue and save the configuration.
Comments
APAR Information
APAR number
PH05525
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-11-21
Closed date
2019-03-01
Last modified date
2019-03-01
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
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R850 PSY
UP
R900 PSY
UP
Document Information
Modified date:
28 April 2022