Fixes are available
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.5.0.1: WebSphere Application Server V8.5 Fix Pack 1
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
Error Description￘ Updates are needed to the following code: com/ibm/ws/sib/jfapchannel/JFapChannelConstants.getSegmentName ( I ) that a) make the method to determine the Segment name more performant and then b) make sure we only call this method when we know we are actually going to use the data (i.e when tracing is on). This section of the code was shown through JPROF to be consuming 20-25% of the CPU during the application's peak usage.
Local fix
Local Fix￘ Tracing on the application server can be temporarily disabled to alleviate the problem.
Problem summary
**************************************************************** * USERS AFFECTED: Users of the default messaging provider * * for * * IBM WebSphere Application Server * **************************************************************** * PROBLEM DESCRIPTION: When using the default messaging * * provider (Service Integration Bus) of * * WebSphere Application Server, a * * perfomance degradation is observed * * when any kind of tracing is enabled * * and whenever there is interaction * * between the server hosting the * * messaging engine and the client. It * * was observed that during peak usage, * * the CPU consumption was 20 to 25%. * **************************************************************** * RECOMMENDATION: * **************************************************************** Performance degradation is observed when any kind of tracing is enabled while using the default messaging provider of WebSphere Application Server and there is interaction between the server hosting the messaging engine and the client. Basically, there is a method that is responsible for returning the segment name based on segment type and this information of segment name obtained during an server-client interaction (JFAP Exchange) is mainly used for debugging purposes. Everytime the segment name is obtained, reflection was made use of to obtain an array of all the declared fields in that class and iterate over each field to find the matching segment value. This implementation of fetching the segment name was causing a performance overhead as every call to get the segment name resulted in reflection being used to obtain an array and iterate over the array to fetch the segment name based on segment type.
Problem conclusion
The code has been modified to ensure that the reflection is used only once and not everytime we fetch the segment name for a given segment type. The fix for this APAR is currently targeted for inclusion in fix packs 6.1.0.45, 7.0.0.25 and 8.0.0.5. 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
PM51216
Reported component name
PLAT MSG COM
Reported component ID
620600101
Reported release
200
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-10-31
Closed date
2012-04-25
Last modified date
2012-09-20
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
PLAT MSG COM
Fixed component ID
620600101
Applicable component levels
R200 PSY
UP
Document Information
Modified date:
28 October 2021