PQ99684: HIGH CPU USAGE WHEN USING THE PROCESS CHOREOGRAPHER PROVIDED WITH WBI-SF 5.1.1 IF THE APPLICATION SERVER IS IDLE | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description When using the Process Choreographer provided with WebSphere Business Integration Server Foundation Version 5.1.1, the CPU usage is quite high even when the application server is sitting idle.Local fix Problem summary **************************************************************** * USERS AFFECTED: This problem affects customers who use the * * Process Choreographer provided with * * WebSphere Business Integration Server * * Foundation (WBI-SF) Version 5.1.1, or the * * non-asf mode for the Java Message Service * * (JMS) functionality provided with WebSphere * * Application Server Version 5.1.x. * **************************************************************** * PROBLEM DESCRIPTION: When using the Process Choreographer * * provided with WebSphere Business * * Integration Server Foundation Version * * 5.1.1, the CPU usage is quite high * * even when the application server is * * sitting idle. * **************************************************************** * RECOMMENDATION: * **************************************************************** The Process Choreographer uses "non-ASF mode" message listeners provided with WebSphere Application Server in order to detect incoming messages. When using this mode, each message listener will wait for a period of time for messages to arrive (this time period is specified by the Message Listener Service custom property "non.asf.receive.timeout"). If no message arrives in this time, the application server will rollback any active transaction before waiting for a new message. It is safe to do this as a new transaction is created immediately before the listener waits for a message - if a timeout occurs waiting for a message, then no work has actually been done. Unfortunately, rolling back an active transaction has quite a large performance overhead.Problem conclusion Rather than rolling back the transaction, the fix simply perfoms a commit, which is less performance intensive. The fix for this APAR is currently targeted for inclusion in Cumulative Fix 4 for WebSphere Application Server Version 5.1.1 and Cumulative Fix 3 for WebSphere Application Server Version 6.0.0. Please refer to the Recommended Updates page for delivery dates: http://www-1.ibm.com/support/ docview.wss?rs=180&context=SSEQTP&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: 10W
Software edition:
Reference #: PQ99684
IBM Group: Software Group
Modified date: Mar 9, 2005
(C) Copyright IBM Corporation 2000, 2008. All Rights Reserved.