PK15961: HIGH CPU UTILIZATION CAUSED BY THE DATA REPLICATION SERVICE | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description If you configured DRS replication service in WebSphere V5.x cluster environment, you may experience a high CPU utilization for WebSphere AppServer JVM where you configured DRS service. . If you take several javacores from the Application Server JVM which has a high CPU utilization, you may observe this Java stack in them: . "Alarm : 2" (TID:40BC2E68, sys_thread_t:8E10CD8, state:R, native ID:1B8010) prio=5 at java.util.LinkedList$ListItr.hasNext(LinkedList.java(Compiled Code)) at com.ibm.ws.drs.DRSPeerCoordinator.pingPeers(DRSPeerCoordinator.j ava(Compiled Code)) at com.ibm.ws.drs.DRSCacheApp.pingPeers(DRSCacheApp.java(Compiled Code)) at com.ibm.ws.drs.DRSPeerCoordinator.alarm(DRSPeerCoordinator.java( Compiled Code)) at com.ibm.ejs.util.am._Alarm.run(_Alarm.java(Compiled Code)) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java(Compiled Code))Local fix N/A. The only way how to recover from a high CPU utilization is to recycle the JVM/AppServer.Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * using HTTP Session memory-to-memory * * replication. * * * **************************************************************** * PROBLEM DESCRIPTION: High CPU utilization may occur when * * using the data replication service. * **************************************************************** * RECOMMENDATION: * * * **************************************************************** When the data replication service (DRS) determines that one of its partner servers is no longer available a message is sent to the remaining partners. High CPU utilization has been observed when performing this procedure. The problem was caused by using a list iterator to notify partner servers.Problem conclusion The process of notifying partner servers has been changed to avoid using a list iterator and use the linked list directly. This will avoid the high CPU utilization in the list iterator. This fix for this APAR is targeted for inclusion in fixpack 5.0.2.16 and 5.1.1.10. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
Publications Referenced
|
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 10I
Software edition:
Reference #: PK15961
IBM Group: Software Group
Modified date: Feb 8, 2006
(C) Copyright IBM Corporation 2000, 2008. All Rights Reserved.