Fix (APAR): PK47882 Status: Fix Release: 6.1.0.13,6.1.0.11 Operating System: AIX,HP-UX,i5/OS,Linux,Linux pSeries,Linux zSeries,OS/400,Solaris,Windows Supersedes Fixes: CMVC Defect: PK47882 Byte size of APAR: 33581 Date: 2007-12-17 Abstract: APAR PK35426 introduced the "write timeout" property that can be set for Web Services application only programmatically. Description/symptom of problem: PK47882 resolves the following problem: ERROR DESCRIPTION: PK35426 introduced the "write timeout" property that can only be set programatically for Web Services applications. More info about the write timeout property & PK35426 is here: http://www-1.ibm.com/support/docview.wss?uid=swg24014268 . Currently this property can be set only by one of the following methods: ========================================================= . 1) via stub for example: --------------- Stub myStub = getStub(); myStub.setWriteTimeout(200000); myStub.setTimeout(200000); . 2) via Call object with DII programming model for example: --------------- Call.setWriteTimeout(new Integer(300000)); . 3) via MessageContext using handler for example: -------------- MessageContext.setWriteTimeout(new Integer(100000)); or MessageContext.setWriteTimeout(100000); . 4) via MessageContext using handler for example: ------------------ msgContext.setProperty(com.ibm.wsspi.webservices.Constants.WRITE_TIMEOUT_PROPERTY, timeout); . This APAR will enable setting the "write timeout" property for Web Services applications via a JVM property in the stand-alone JVM or for all applications that are deployed in the same WebSphere Application server JVM. . This "write timeout" property can be also set declaratively for the specific Web Services application that is deployed in WebSphere application server via the application deployment descriptor. LOCAL FIX: To set "write timeout" property programatically. PROBLEM SUMMARY USERS AFFECTED: IBM WebSphere Application Server version 6.0.2 and 6.1 users of web services. PROBLEM DESCRIPTION: PK35426 introduced the "write timeout" property that can only be set programatically for Web Services applications. RECOMMENDATION: None APAR PK35426 introduced the "write timeout" property that can be set programmatically. Request is to add ability to control the timeout with a property. PROBLEM CONCLUSION: The write timeout can now be set with a property in the Deployment Descriptor (DD) or a JVM property. The DD setting will override a JVM property. The property name is com.ibm.ws.webservices.writeTimeout. To set the DD value, open the DD in RAD and go to the WSBinding tab. Then look for Parameters of Port Qualified Name Binding. Add the property and the value is specified in seconds. This fix is scheduled for fixpacks 6.0.2.27 and 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: