PM72328: CWSIK0022E ERRORS AFTER FAILBACK OF WEBSPHERE APPLICATION SERVER SERVICE INTEGRATION BUS MESSAGING ENGINE

Fixes are available

APAR status

Closed as program error.

Error description

In WebSphere Application Server two node cluster Bus member
the messaging engine successfully starts up on member1. After
shutting down member1, the messaging engine successfully
fails over to member2, but later when the messaging engine
is failed back to member1 the JMS application fails to
reconnect to the messaging engine and the following errors
are logged in the SystemOut.log:

On the JVM hosting the JMS application:
CWSJR1067E:The following JCA Connection error has occurred
when trying to get the connection. The retrieving of the
connection will be retried. The exception is com.ibm.wsspi.
sib.core.exception.SIConnectionUnavailableException:CWSIC8007E:
An exception was caught from the remote server with Probe Id
3-006-0002. Exception: CWSIK0022E: The connection is closed
to messaging engine XXX and cannot be used...
CWSIA0067E: An exception was received during the call to the
method JmsMsgProducerImpl.<constructor>:com.ibm.wsspi.sib.
core.exception.SIConnectionUnavailableException:CWSIC8007E:
An exception was caught from the remote server with Probe
Id 3-008-0001. Exception: CWSIK0022E: The connection is
closed to messaging engine XXX and cannot be used...

On the JVM hosting the failedback messaging engine:
CWSIK0022E: The connection is closed to messaging engine
XXX and cannot be used.


FFDCS are produced with the following stack:

com.ibm.ws.sib.processor.exceptions.SIMPConnectionUnavailable
Exception SourceId:com.ibm.ws.sib.comms.server.clientsupport.
StaticCATConnection.rcvCloneConnection ProbeId:3-006-0002
com.ibm.ws.sib.processor.exceptions.SIMPConnection
UnavailableException: CWSIK0022E: The connection is closed to
messaging engine XXX and cannot be used.
at com.ibm.ws.sib.processor.impl.ConnectionImpl.checkNotClosed
  (ConnectionImpl.java:324)
at com.ibm.ws.sib.processor.impl.ConnectionImpl.clone
  Connection(ConnectionImpl.java:3863)
at com.ibm.ws.sib.comms.server.clientsupport.StaticCAT
  Connection._cloneConnection(StaticCATConnection.java:451)
at com.ibm.ws.sib.comms.server.clientsupport.StaticCAT
  Connection.rcvCloneConnection(StaticCATConnection.java:383)
at com.ibm.ws.sib.comms.server.clientsupport.ServerTransport
  ReceiveListener.dataReceived(ServerTransportReceiveListener.
  java:400)
at com.ibm.ws.sib.jfapchannel.impl.rldispatcher.Conversation
  ReceiveListenerDataReceivedInvocation.invoke(Conversation
  ReceiveListenerDataReceivedInvocation.java:195)
at com.ibm.ws.sib.jfapchannel.impl.rldispatcher.Receive
  ListenerDispatchQueue.run(ReceiveListenerDispatchQueue.
  java:542)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.
  java:1613)

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  Users of the default messaging provider     *
*                  for IBM WebSphere Application Server V7.0,  *
*                  V8.0 and V8.5                               *
****************************************************************
* PROBLEM DESCRIPTION: CWSIK0022E exceptions seen in the log   *
*                      after messaging engine has failed       *
*                      back to the preferred server.           *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Under a WebSphere Application Server cluster a bus member
topology is configured with a high availability policy. If a
preferred server is selected then the messaging engine starts
up on the preferred server . When the preferred server is
stopped, the messaging engine fails over to another member of
the cluster. Once the preferred server is restarted, the
messaging engines would move back to the preferred server
again. In this case when the connection to the Messaging
Engine that was running on a non-preffered server and during
the usage of the connection,  if the Messaging Engine fails
back to the preferred server then connections from JMS
applications to the Messaging Engine can result in the
following exception in the logs:
CWSIK0022E: The connection is closed to messaging engine XXX
and cannot be used.

Problem conclusion

This APAR solves the problem by sending the messaging engine
stop events to the connection pool during the fail back
event. This would mark the connection as a stale connection
and would prevent it from going into an exception state.

The fix for this APAR is currently targeted for inclusion in
fix packs 7.0.0.29, 8.0.0.6 and 8.5.0.2. 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
PM72328
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
2012-09-06
Closed date
2012-12-05
Last modified date
2012-12-05

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

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 October 2021

Tips

PM72328: CWSIK0022E ERRORS AFTER FAILBACK OF WEBSPHERE APPLICATION SERVER SERVICE INTEGRATION BUS MESSAGING ENGINE

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R800 PSY

Document Information

Share your feedback

Need support?