Fixes are available
PI15205;8.5.5: cannot connect to messaging engine after failover
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
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.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
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.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
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
A messaging engine stopped on one cluster member due to database errors. The messaging engine subsequently started successfully on another cluster member. However other servers within the cell cannot connect to it. Possible symptom message: CWSIT0019E: No suitable messaging engine is available on bus <b> that matched the specified connection properties <p> Traces for WLM*=all show the following exception occurring repeatedly: com.ibm.ws.cluster.selection.NoAvailableTargetExceptionImpl Within the detailed exception message, the string "removed: no CFEndPoint matching criteria" appears.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server * **************************************************************** * PROBLEM DESCRIPTION: Client cannot connect to messaging * * engine after it fails over * **************************************************************** * RECOMMENDATION: * **************************************************************** A messaging engine stopped due to database errors. It subsequently started successfully on another cluster member. However clients cannot connect to it. Possible symptom message: CWSIT0019E: No suitable messaging engine is available on bus <b> that matched the specified connection properties <p> Traces for WLM*=all show the following exception occurring repeatedly: com.ibm.ws.cluster.selection.NoAvailableTargetExceptionImpl Within the detailed exception message, the string "removed: no CFEndPoint matching criteria" appears.
Problem conclusion
The code has been changed to correct a specific cause of this problem. This is a difficult problem to identify because there are other valid causes for the symptom message CWSIT0019E to appear. There are also other valid causes for the exception NoAvailableTargetExceptionImpl to appear in traces with the reason "removed: no CFEndPoint matching criteria". The problem occurs because an incorrect relationship forms between two objects, the RuleEtiquette and the ChannelTargetRule. It may only be possible to observe the incorrect relationship by having WLM traces active at the time the messaging engine fails over. The specific trace sequence is shown below. [3/25/14 23:06:08:106 CST] 00000024 RuleEtiquette > handleNotification Entry {CELL=PSCell1, COMPONENT=CF, NAME=InboundSecureMessaging, NODE=Node2, SERVER=MEClusterMember2, TYPE=CHANNEL} type.memento.updated [EndPointImpl$MementoImpl#-415927217{CELL=PSCell1, COMPONENT=CF, NAME=InboundSecureMessaging, NODE=Node2, SERVER=MEClusterMember2, TYPE=CHANNEL}][true::{CELL=PSCell1, COMPONENT=CF, NAME=InboundSecureMessaging, NODE=Node2, SERVER=MEClusterMember2, TYPE=CHANNEL}:false] <null> [3/25/14 23:06:08:106 CST] 00000024 RuleEtiquette 3 working on rule [email protected] luster.channel.ChannelTargetRule@-9250769 [cfEndPointCriteria=com.ibm.wsspi.cluster.adapter.channel.Channe lSelectionCriteria@de6b082a [clusterIdentity={bus=BPM.De1.Bus, name=MECluster, type=WSAF_SIB_BUSMEMBER}] [criteria = com.ibm.ws.cluster.selection.SelectionCriteriaImpl@472ee3c0[{bus =BPM.De1.Bus, name=MECluster, type=WSAF_SIB_BUSMEMBER}:{rules.precedence=[Lcom.ibm.wsspi.clust er.selection.SelectionRule;@3e68712a, AcceptableStates=[B@b23436e3, rules.restriction=[Lcom.ibm.wsspi.cluster.selection.SelectionRul e;@8d7df22b}]] [chainName=InboundSecureMessaging] [sslRequired=false] [accessor=null] [channelFactories={null}] [3/25/14 23:06:08:106 CST] 00000024 RuleEtiquette 3 rule class name is com.ibm.ws.cluster.channel.ChannelTargetRule [3/25/14 23:06:08:106 CST] 00000024 ChannelTarget > subset Entry [{bus=BPM.De1.Bus, name=MECluster.000-BPM.De1.Bus, subnet=, type=WSAF_SIB_ME_LONG_NAME}] [3/25/14 23:06:08:106 CST] 00000024 ChannelTarget < subset Exit [{bus=BPM.De1.Bus, name=MECluster.000-BPM.De1.Bus, subnet=, type=WSAF_SIB_ME_LONG_NAME}] The key points in this trace are: 1) Entry to RuleEtiquette.handleNotification() with one of the arguments being type.memento.updated. followed by 2) Entry to ChannelTargetRule.subset() with a cluster identity that does not represent an application server (i.e. something like [{CELLNAME=PSCell1, MEMBERNAME=MEClusterMember2, NODENAME=Node2}]). This shows the incorrect relationship exists between the RuleEtiquette and ChannelTargetRule objects. The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.3. 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
PI15205
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-04-04
Closed date
2014-05-02
Last modified date
2014-05-02
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
Document Information
Modified date:
28 April 2022