Fix (APAR):  PK20275

Status:  Fix

Release:  5.1.1.9,5.1.1.8

Operating System:  AIX,HP-UX,Linux,Linux Red Hat - pSeries,Linux zSeries,OS/390,OS/400,Solaris,Windows,z/OS

Supersedes Fixes:  

CMVC Defect:  PK20275

Byte size of APAR:  7778

Date: 2006-03-01

Abstract:  SOAPMessage.writeTo in Handler Causes a Protected State Violation

Description/symptom of problem:  
PK20275 resolves the following problem:

ERROR DESCRIPTION:                                              
Problem:                                                        
SOAPMessage.writeTo in Handlerb causes Protected state          
violation.  (JSR 109, Web services for J2EE, Version 1.0,       
6.2.2.2) if the message contains attachments.                   
                                                                
                                                                
  [3.2.2006 17:04:01:690 CET]  4520452 PivotHandlerW E          
  com.ibm.ws.webservices.engine.PivotHandlerWrapper  WSWS3400I: 
  Info: unexpected exception.                                   
                                                                
  [3.2.2006 17:04:01:721 CET]  4520452 PivotHandlerW E          
  com.ibm.ws.webservices.engine.PivotHandlerWrapper  TRAS0014I: 
  The following exception was logged                            
  javax.xml.rpc.soap.SOAPFaultException:                        
  WSWS3396E: Error: Handler                                     
  com.cna.service.attachments.handler.CFServerAttachmentHandler:
  Protectedstate violation.                                     
  (JSR 109, Web services for J2EE, Version 1.0,6.2.2.2).        

LOCAL FIX:                                                      
none                                                            

PROBLEM SUMMARY

USERS AFFECTED:
WebSphere Application Server users of web
services

PROBLEM DESCRIPTION:
SOAPMessage.writeTo in Handler Causes
a Protected State Violation

RECOMMENDATION:
None

SOAPMessage.writeTo in Handler Causes a Protected State
Violation if the Message Contains Attachments using SAAJ on
the client side.  The Message encoding should default to UTF-8
if HTTPServletRequest.getCharacterEncoding() returns null.

PROBLEM CONCLUSION:                                             
The Message encoding will default to UTF-8 if                   
HTTPServletRequest.getCharacterEncoding() returns null.         
                                                                
The fix for this APAR is currently targeted for inclusion       
in cumulative fix 5.1.1.10.                                     
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:
5.0  5.1
___  ___ Application Server (Express or BASE)
___      Enterprise Edition (DD)
___  ___ Network Deployment (ND)
___  ___ Edge Components
___  ___ Developers Edition
___  ___ Tools
     ___ WebSphere Business Integration Server Foundation (WBISF)

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.
* Be logged in with the same authority level when unpacking a fix, fix pack or refresh pack.

The Update Installer can be downloaded from the following link:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991

The Update Installer for V5.0 does not have a maintenance directory.
It uses fixpacks and fixes as the location of the unpacked files.

1) Copy PKxxxxx.jar 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.jar file which was copied in the maintenance directory).
The V5.0 and V5.1 fix packs and fixes are unpacked as .jar files and should be unpacked into fixpacks or fixes 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.jar).

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: