Fix (APAR):  PI15518

Status:  Fix

Release:  8.5.5.2

Operating System:  AIX,HP-UX,IBM i,Linux,Solaris,Windows,z/OS

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  277990

Date: 2014-06-10

Abstract:  notifications not sent to service integration bus clients when a messaging engine instance is stopped forcefully

Description/symptom of problem:  
PI15518 resolves the following problem:

ERROR DESCRIPTION:                                              
Notifications not sent to Service Integration Bus clients when  
a messaging engine instance is stopped forcefully.              

LOCAL FIX:                                                      
                                                                

PROBLEM SUMMARY

USERS AFFECTED:
 Users of the default messaging provider for
IBM WebSphere Application Server V8.5

PROBLEM DESCRIPTION:
When messaging engine receives
FORCE_STOP request, clients which
are connected to the messaging engine
are not notified about the stop event.
As a result, the client will not be
able to connect to messaging engine
after messaging engine fails over to
another member in cluster. Since the
clients are not notified about the
stop event, they would still use the
existing connection that has been
established previously and
SIConnectionUnavailableException and
SIMPConnectionUnavailableException
will be thrown in the logs

RECOMMENDATION:
None

In a WebSphere Application Server Service Integration Bus,
when a messaging engine loses a connection to datastore it
will try to re-establish a connection to the datastore for 15
minutes. If unsuccessful then the messaging engine receives a
FORCE_STOP request and goes to disabled state but connected
clients will not be notified about the messaging engine stop
event. Since the clients are not notified about the stop
event, they would still use the existing connection that has
been established previously, leading to
SIConnectionUnavailableException and
SIMPConnectionUnavailableException in the logs.
com.ibm.wsspi.sib.core.exception.SIConnectionUnavailableExceptio
n: CWSIC8007E:  An exception was caught from the remote server
with ID 3-008-0001 Exception: CWSIK0022E: The connection is
closed to messaging engine CL_BPWH01.000-BPM.De1.Bus and
cannot be used....
at
com.ibm.ws.sib.comms.common.CommsByteBuffer.parseSingleException
(CommsByteBuffer.java:1810)
at
com.ibm.ws.sib.comms.common.CommsByteBuffer.getException(CommsBy
teBuffer.java:1263)
at
com.ibm.ws.sib.comms.common.JFAPCommunicator.checkFor_SIConnecti
onUnavailableException(JFAPCommunicator.java:1300)
at
com.ibm.ws.sib.comms.client.ConnectionProxy._createConsumerSessi
on(ConnectionProxy.java:1269)
at
com.ibm.ws.sib.comms.client.ConnectionProxy.createConsumerSessio
n(ConnectionProxy.java:943)
at
com.ibm.ws.sib.api.jms.impl.JmsMsgConsumerImpl.createCoreConsume
r(JmsMsgConsumerImpl.java:1048)
........

PROBLEM CONCLUSION:                                             
We will now send stop event notifications to messaging          
engine clients when the messaging engine receives a FORCE_STOP  
request.                                                        
                                                                
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   


Directions to apply fix:  


Fix applies to Editions:
Release 8.5.5.2
X__ Application Server (Express or BASE)
X__ Network Deployment (ND)


Install Fix to all WebSphere installations unless special instructions are included below.

Special Instructions: None

NOTE:
The user must:
* Logged in with the same authority level when unpacking a fix, fix pack or refresh pack.
* Be at V1.4.3 or newer of the Installation Manager. Certain iFixes may require a newer version of the Installation Manager and the Installation Manager will inform you during the installation process if a newer version is required.

The IBM Information Center can provide details, if needed, on the use of the Installation Manager to apply the iFixes.
http://publib.boulder.ibm.com/infocenter/install/v1r4/index.jsp.  Shutdown WebSphere Application Server before applying the iFixes.  Restart WebSphere Application Server after applying the iFixes.

Directions to remove fix:  

The IBM Information Center can provide details, if needed, on the use of the Installation Manager to remove the iFixes.
http://publib.boulder.ibm.com/infocenter/install/v1r4/index.jsp.  Shutdown WebSphere Application Server before removing the iFixes.  Restart WebSphere Application Server after removing the iFixes.

Directions to re-apply fix:  
1) Shutdown WebSphere Application Server.

2) Follow the Fix instructions to apply the fix.

3) Restart WebSphere Application Server.



Additional Information: