Fixes are available
8.5.5.1: WebSphere Application Server V8.5.5 Fix Pack 1
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
8.5.5.2: WebSphere Application Server V8.5.5 Fix Pack 2
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
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.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
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.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
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
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
Obtain the fix for this APAR.
APAR status
Closed as program error.
Error description
When a call stack exceeds the buffer size, the entry in the SYSPRINT log is truncated with the message ***BUFFER OVERFLOW*** and the full call stack is unavailable. This APAR will change the behavior to generate an ffdc log with the full call stack.
Local fix
The custom property private_bbor_bborto_max_str can be used to increase the buffer size. Set this variable using the adminconsole along this path: Environment > WebSphere Variables > {set node scope} > click New button Name private_bbor_bborto_max_str Please note that use of this private environment variable is only recommended for debug purposes. Initially set the value to 131072 (128K) and see if the Buffer Overflow condition persists. If it does, continue increasing the value in 128K increments until the Buffer Overflow condition is resolved. Once the appropriate data is obtained, the variable should be deleted to ensure that future tracing uses the default buffer size, thereby avoiding unnecessary spool. You need to restart the server to pick these changes up.
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V7.0, V8.0, and V8.5 * **************************************************************** * PROBLEM DESCRIPTION: Some trace entries in the SYSPRINT * * log are truncated showing the string: * * ***BUFFER OVERFLOW*** * **************************************************************** * RECOMMENDATION: * **************************************************************** Some trace entries in the SYSPRINT log do not display the complete trace data. The string ***BUFFER OVERFLOW*** appears at the end of the truncated trace. This happens because, in some instances, the amount of data being traced exceeds the size of internal predefined trace buffers used for logging. This prevents important debug information from being readily available for issues encountered during workload processing.
Problem conclusion
Trace entries that experience the mentioned condition during workload processing will have its data written to a ffdc log. The ffdc log created will report the the following exception: com.ibm.ejs.ras.NativeMessageOverflowException. Truncated traces in the SYSPRINT log will show a new string: ***BUFFER OVERFLOW***TRACE DATA ROUTED TO FFDC REPORTING A NativeMessageOverflowException*** APAR PM88159 is currently targeted for inclusion in Fix Packs 7.0.0.31, 8.0.0.8, and 8.5.5.1 of WebSphere Application Server. Please refer to URL: //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970 for Fix Pack availability.
Temporary fix
Comments
APAR Information
APAR number
PM88159
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2013-04-30
Closed date
2013-06-27
Last modified date
2014-02-05
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
WEBSPHERE FOR Z
Fixed component ID
5655I3500
Applicable component levels
R700 PSY UI13725
UP14/01/11 P F401
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
Document Information
Modified date:
11 January 2022