Fix (APAR): PK53885 Status: Fix Release: 6.1.0.11 Operating System: AIX,HP-UX,i5/OS,Linux,OS/400,Solaris,Windows Supersedes Fixes: CMVC Defect: PK53885 Byte size of APAR: 18781 Date: 2007-10-10 Abstract: Resource unexpectedly receives either a "writer already obtained" error or an "Outputstream already obtained" error. Description/symptom of problem: PK53885 resolves the following problem: ERROR DESCRIPTION: A servlet receives an IllegalStateException: writer already obtained when calling response.getOutputStream() for the first time in a request. LOCAL FIX: N/A PROBLEM SUMMARY USERS AFFECTED: IBM WebSphere Application Server version 6.1 users with resources which use a HttpResponse object to obtain a writer or an Ouputstream. PROBLEM DESCRIPTION: Resource unexpectedly receives either a "writer already obtained" error or an "Outputstream already obtained" error. RECOMMENDATION: None The problem occurs following an exception during commit of a response. For example if the exception call stack includes: com.ibm.ws.webcontainer.srt.SRTServletResponse.commit (SRTServletResponse .java:xxx) at com.ibm.ws.webcontainer.srt.SRTServletResponse.finish (SRTServletResponse .java:xxx) the response object is not fully cleared for re-use by a subsequent request. As a result, response settings for the request which received the exception are still in place for a subsequent request which is allocated the same response object. The settings which remain are: - whether or not getWriter() was used to obtain a writer. - whether or not getOutputStream() was used to obtain an Outputstream. - the buffer size which was used. - the encoding which was used. - the address of a print writer if used The first two will cause the error reported: [9/14/07 13:13:28:484 EDT] 0000001e SystemErr R java.lang.IllegalStateException: SRVE0209E: Writer already obtained The other three could result in a request using incorrect response settings. PROBLEM CONCLUSION: The webcontainer has been updated to ensure that a response object is fully reset before it is allocated for used by a new request. The fix for this APAR is currently targeted for inclusion in fixpack 6.1.0.15. Please refer to the recommended updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 Directions to apply fix: NOTE: Choose the: 1) Release the fix applies to 2) The Editions that apply 3) Delete the Editions & Methods that do not apply and this Note Fix applies to Editions: Release 6.0 __ Application Server (Express or BASE) __ Network Deployment (ND) __ WebSphere Business Integration Server Foundation (WBISF) __ Edge Components __ Developer __ Extended Deployment (XD) Install Fix to: Method: __ Application Server Nodes __ Deployment Manager Nodes __ Both NOTE: The user must: * Have Administrative rights in Windows, or be the Actual Root User in a UNIX environments. * Logged in with the same authority level when unpacking a fix, fix pack or refresh pack. * Be at V6.0.2.2 or newer of the Update Installer. This can be checked by reviewing the level of the Update Installer in file /updateinstaller/version.txt. The Update Installer can be downloaded from the following link: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991 For detailed instructions to Extract the Update Installer see the following Technote: http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg21205400 1) Copy PKxxxxx.pak file directly to the maintenance directory 2) Shutdown WebSphere Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that maintenance is being applied to. 3) Launch Update Installer 4) Enter the installation location of the WebSphere product you want to update. 5) Select the "Install maintenance package" operation. 6) Enter the file name of the maintenance package to install (PKxxxxx.pak file which was copied in the maintenance directory). 7) Install the maintenance package. 8) Restart WebSphere Directions to remove fix: NOTE: * The user must have Administrative rights in Windows, or be the Actual Root User in a UNIX environments. * FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED * DO NOT REMOVE A FIX UNLESS ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED * YOU MAY REAPPLY ANY REMOVED FIX Example: If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be removed, fix3 must be removed first, fix2 removed, and fix3 re-applied. 1) Shutdown WebSphere Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that uninstall is being run against. 2) Start Update Installer 3) Enter the installation location of the WebSphere product you want to remove the fix. 4) Select "Uninstall maintenance package" operation. 5) Enter the file name of the maintenance package to uninstall (PKxxxxx.pak). 6) UnInstall maintenance package. 7) Restart WebSphere Directions to re-apply fix: 1) Shutdown WebSphere. 2) Follow the Fix instructions to apply the fix. 3) Restart WebSphere. Additional Information: