Fix (APAR): PM07249
Status: Fix
Release: 6.1.0.27,6.1.0.25
Operating System: AIX,HP-UX,i5/OS,Linux,Solaris,Windows
Supersedes Fixes: PK95980
CMVC Defect: PM07249
Byte size of APAR: 142107
Date: 2010-04-12
Abstract: A NullPointerException may occur when a JAX-RPC application receives a message that contains no elements in the SOAP Body.
Description/symptom of problem:
PM07249 resolves the following problem:
ERROR DESCRIPTION:
A NullPointerException error may occur when a JAX-RPC
application receives a message from a web service.
Example error:
[2/5/10 16:51:23:076 GMT+05:30] 0000003f Connection E
com.ibm.ws.webservices.engine.client.Connection invoke
WSWS3227E:
Error: Exception: java.lang.NullPointerException
at
com.ibm.ws.webservices.engine.utils.MCUtils.interceptDeserializa
tionException(MCUtils.java:181)
at
com.ibm.ws.webservices.engine.xmlsoap.ext.RequestResponse.deseri
alize(RequestResponse.java:439)
at ...
This error only occurs if the response message does not
contain any elements within the SOAPBody. For example:
Hello
LOCAL FIX:
no local fix avail at this time
PROBLEM SUMMARY
USERS AFFECTED:
IBM WebSphere Application Server V6.1 and
V7.0 users of JAX-RPC
PROBLEM DESCRIPTION:
A NullPointerException may occur when
a JAX-RPC application receives a
message that contains no elements
in the SOAP Body.
RECOMMENDATION:
None
A JAX-RPC client application invokes a two-way document
literal wrapped operation of a remote web service.
Here is an example outgoing message:
Hello
The JAX-RPC client runtime expects a response that contains a
myOperationResponse object (even if the web service does not
pass back any data). Instead the response contains a SOAP
Body without any contents. For example:
This incoming message is unexpected and results in a
NullPointerException error.
PROBLEM CONCLUSION:
The JAX-RPC client runtime is changed to correctly process the
incoming message.
If the incoming message contains no elements in the SOAP Body
and output data was expected, then the client runtime will now
issue an informative error.
If the incoming message contains no elements in the SOAP Body
and output data was not expected, then the client runtime will
tolerate the incoming message and proceed without error.
The fix for this APAR is currently targeted for inclusion in
fix packs 6.1.0.33 and 7.0.0.11. 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: Fix applies to Editions:
Release 6
_X_ Application Server (Express or BASE)
_X_ 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
_X_ 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.1.0.13 or newer of the Update Installer. Certain iFixes may require a newer version of the Update Installer and the Update Installer will inform you during the installation process if a newer version is required. 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.ibm.com/support/docview.wss?rs=180&uid=swg21205400
Note that there are two different methods for delivering iFixes, depending on the contents. The fix may be delivered either as a single file with a .pak extension (such as 6.1.0.11-WS-WAS-IFPK12345.pak) or a single file with a .zip extension (such as 6.1.0.11-WS-WAS-IFPK12345.zip) which then contains one or more files with a .pak extension.
1) If your iFix is delivered as a single file with a .pak extension, Copy the .pak file directly to the maintenance directory. If your iFix is delivered as a single file with a .zip extension, unzip the file into 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 and click the Next button on the Welcome page.
4) Enter the directory path of the installation location of the WebSphere product you want to update, and click the Next button.
5) Select the "Install maintenance package" operation and click the Next button.
6) Enter the directory path of your maintenance directory where you have the maintenance packages (.pak files) and click the Next button.
7) The Available Maintenance Package to Install page should list all maintenance packages (.pak files) that it finds in the directory path provided in the previous step.
The Update Installer will select the correct maintenance packages based on your system configuration and will not allow an invalid combination to be installed. Please keep the Update Installer recommendations and click the Next button and continue with the installation of the maintenance package.
8) Please note that in the future, if a Feature Pack is installed or uninstalled, a different set of iFixes will be needed. Use the Update Installer again at that time, with the maintenance directory location where these maintenance packages are stored, to determine the required interim fixes for the new WebSphere and Feature Pack(s) combination.
9) The maintenance packages could have one of a set of names, and these names will help determine which maintenance package you need to install. The APAR name (PKxxxxx) should appear as part of the filename. Between the APAR number and the .pak extension there will be 0 to 2 characters added. The table below indicates the usage of each of the maintenance packages with respect to which Feature Packs, if any, are installed.
|.pak File Names |No Feature Packs|EJB3 Only|WebServices Only| Both |
|6.1.0.x-WS-WAS-IFPK12345 | X | X | X | X |
|6.1.0.x-WS-WAS-IFPK12345C | X | | | |
|6.1.0.x-WS-WAS-IFPK12345CE | | X | X | X |
|6.1.0.x-WS-WAS-IFPK12345W | X | X | | |
|6.1.0.x-WS-WAS-IFPK12345WE | | | X | X |
|6.1.0.x-WS-WAS-IFPK12345E | X | | X | |
|6.1.0.x-WS-WAS-IFPK12345EE | | X | | X |
10) 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 Application Server.
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) Select file name of the maintenance package to uninstall (for example, 6.1.0.11-WS-WAS-IFPK12345.pak).
6) Verify the Uninstallation Summary and continue with the uninstall.
7) Restart WebSphere
Directions to re-apply fix:
1) Shutdown WebSphere Application Server.
2) Follow the Fix instructions to apply the fix.
3) Restart WebSphere Application Server.
Additional Information: