Fixes are available
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
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.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
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
Obtain the fix for this APAR.
APAR status
Closed as program error.
Error description
System.out.checkError() always returns false. The checkError() call will return true when the underlying stream cannot be used due to error. Thus, any check of the PrintStream will indicate that the stream is fine and ready for use, even if the stream cannot be used due to error.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application Server * V6.1.0 * **************************************************************** * PROBLEM DESCRIPTION: Can not detect when System.out.println * * requests are not being written to * * the HFS file pointed to by SYSPRINT. * **************************************************************** * RECOMMENDATION: * **************************************************************** System.out.checkError() does not return true after a System.out.println fails because the HFS is full.
Problem conclusion
Changed the code so checkError() will return true when the underlying stream encountered an error. A new property server_wto_on_write_error can be set to cause the BBOO0384I message to be written when there was an error writing to SYSPRINT or SYSOUT. APAR PM25806 requires changes to documentation. NOTE: Periodically, we refresh the documentation on our Web site, so the changes might have been made before you read this text. To access the latest on-line documentation, go to the product library page at: http://www.ibm.com/software/webservers/appserv/library The following changes to the z/OS version of the WebSphere Application Server Version 6.1 Information Center will be made available in July, 2011. The following information will be added to the topic "Application server custom properties that are unique for the z/OS platform": server_wto_on_write_error Indicates whether the error message BBOO0384I ERROR OCCURRED WRITING TO {0} is written to the SYSLOG when an error occurs while writing to SYSPRINT or SYSOUT. This property can be set to 0 or 1. When this property is set to 1, this error message is written to the SYSLOG. When this property is set to 0 no message is issued. Data Type Integer Default 0 Used by Daemon No The following information will be added to the table in the topic "Changing the values of variables referenced in BBOM0001I messages:" server_wto_on_write_error In the administrative console, click Servers > Application Servers > server > Server infrastructure > Administration > Custom Properties > New, select the appropriate node or cell from the list of available nodes and cells, and then click New. Add the server_wto_on_write_error property, and specify a different value. Indicates whether the error message BBOO0384I ERROR OCCURRED WRITING TO {0} is written to the SYSLOG when an error occurs while writing to SYSPRINT or SYSOUT. See Application server z/OS custom properties for additional information. The BBOO messages topic under Messages in the Reference section of the Information Center will be updated to include the following new message: BBOO0384I ERROR OCCURRED WRITING TO {0}. Explanation: An error occurred when writing to SYSOUT or SYSPRINT. Programmer response: If SYSOUT or SYSPRINT is being directed to the HFS, free up some space. APAR PM25806 is currently targeted for inclusion in Service Level (Fix Pack) 6.1.0.39 of WebSphere Application Server V6.1. 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
PM25806
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
610
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-11-03
Closed date
2011-02-09
Last modified date
2011-08-01
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
R610 PSY UK69361
UP11/07/16 P F107
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:
27 October 2021