Fix (APAR):  PI32705

Status:  Fix

Release:  8.5.5.3

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

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  271040

Date: 2015-03-30

Abstract:  Large number of TickRange instances under                       GuaranteedTargetStream consumes more memory and may create

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

ERROR DESCRIPTION:                                              
Large number of TickRange instances under one                   
GuaranteedTargetStream instance occupies a major portion of     
JVM heapspace observed under heapdump. High CPU also may be     
observed because of this.                                       

LOCAL FIX:                                                      
None                                                            

PROBLEM SUMMARY

USERS AFFECTED:
 Users of the default messaging provider
for IBM WebSphere Application Server
versions 7.0, 8.0 and 8.5.

PROBLEM DESCRIPTION:
Unnecessary TickRange instances
occupy more heapspace and may create
High CPU.

RECOMMENDATION:
None

When using Publish Subscribe in Service Integration Bus in a
multi Messaging Engine scenario, Heapdump shows large number
of TickRange instances under GuaranteedTargetStream which may
lead to unnecessary consumption of memory and considerable CPU
cycles. One possiblility of having large number of TickRange
instances is when there are a lot of silence messages which
are consecutive are not getting consolidated. So it is not
necessary to have these TickRange instances which belong to
consecutive silence messages.

PROBLEM CONCLUSION:                                             
Source code has been modified by consolidating the silence      
ticks and sending an acknowledgement for those ticks so that    
all "TickRange" instances will be deleted.                      
                                                                
The fix for this APAR is currently targeted for inclusion in    
fix packs 7.0.0.39, 8.0.0.11 and 8.5.5.6.                       
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.0
_x_ Application Server (Express or BASE)
_x_ Network Deployment (ND)
__ Edge Components
__ Developer

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: