Fix (APAR): JR26881 Status: Fix Release: 6.0.2.1 Operating System: AIX,HP-UX,Linux,Solaris,Windows,z/OS Supersedes Fixes: CMVC Defect: xxxxxx Byte size of APAR: 7501 Date: 2007-07-11 Abstract: WS-Import returns extra SessionContext information in the SOAP response Header Description/symptom of problem: JR26881 resolves the following problem: ERROR DESCRIPTION: when calling a web service export that is attached to a long running BPEL process, the response from WPS contains session context information in the SOAP header. This should not be sent out to the external web service client. LOCAL FIX: edit the .export file to suppress this. PROBLEM SUMMARY USERS AFFECTED: WebSphere Process Server 6.0.2.1 users PROBLEM DESCRIPTION: WS-Import returns extra SessionContext information in the SOAP response Header RECOMMENDATION: None When calling a web service export that is attached to a long running BPEL process, the response from WPS contains session context information in the SOAP header. This should not be sent out to the external web service client. Session context was inadvertently returned to external non-SCA client via WS export. This is caused by a logical error in SCA. PROBLEM CONCLUSION: The fix is to construct a message for invokeResponse() using the AsyncInteractionHeader from resultMessage, and rest of the headers from message. Directions to apply fix: Before applying the iFix ensure that WebSphere Process Server 6.0.1 is installed on the system. Also download and follow Update Installer installation instructions. The Update Installer can be downloaded from the following link: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991 1) Copy the pak file to the directory maintenance in the UpdateInstaller directory 2) Shutdown WebSphere Process Server. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix. 3) Run the UpdateInstaller and follow the prompts. 4) Restart WebSphere Directions to remove fix: NOTE: FIXES MUST BE REMOVED IN THE REVERSE ORDER IN WHICH 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, then fix2 may be removed 1) Shutdown WebSphere. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix. 2) Follow the Fix instructions that are packaged with the Fix Installer on how to uninstall and reinstall the Fix. 3) Restart WebSphere Directions to re-apply fix: 1) Shutdown WebSphere. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix. 2) Run the UpdateInstaller and follow the instructions. The Update Installer can be downloaded from the following link: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991 3) Restart WebSphere Process Server Additional Information: