Fixes are available
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
When a JAX-RPC application tries to deserialize a SOAP message with an Axis-style attachment, the following exception may be observed in the JVM log: [10/06/24 16:55:08:796 JST] 0000002b MCUtils com.ibm.ws.webservices.engine.utils.MCUtils interceptDeserializationException interceptDeserializationException: java.lang.RuntimeException: WSWS3250E: Error: AttachmentUtils.getActiviationDataHandler received a null parameter as a part.WebServicesFault faultCode: {http://schemas.xmlsoap.org/soap/envelope/} Server.generalException faultString: WSWS3250E: Error: AttachmentUtils.getActiviationDataHandler received a null parameter as a part. faultActor: null faultDetail: WSWS3250E: Error: AttachmentUtils.getActiviationDataHandler received a null parameter as a part. at com.ibm.ws.webservices.engine.attachments.AttachmentUtils. getActivationDataHandler(AttachmentUtils.java:125) at com.ibm.ws.webservices.engine.encoding.ser. JAFDataHandlerDeserializer. getDataHandler(JAFDataHandlerDeserializer.java:174) at com.ibm.ws.webservices.engine.encoding.ser. JAFDataHandlerDeserializer. makeValue(JAFDataHandlerDeserializer.java:154) at com.ibm.ws.webservices.engine.encoding. ser.SimpleDeserializer. onEndElement(SimpleDeserializer.java:239) at com.ibm.ws.webservices.engine.encoding.Deserializer. endElement(Deserializer.java:675) ... This can happen on either the client or service.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of JAX-RPC applications in IBM * * WebSphere Application Server V7.0 * **************************************************************** * PROBLEM DESCRIPTION: A WSWS3250E error may occur when a * * JAX-RPC application tries to * * deserialize a message with an * * Axis-style attachment. * **************************************************************** * RECOMMENDATION: Install a fixpack that includes this APAR. * **************************************************************** When a JAX-RPC application tries to deserialize a SOAP message with an Axis-style attachment, the following exception may be observed in the JVM log: [10/06/24 16:55:08:796 JST] 0000002b MCUtils com.ibm.ws.webservices.engine.utils.MCUtils interceptDeserializationException interceptDeserializationException: java.lang.RuntimeException: WSWS3250E: Error: AttachmentUtils.getActiviationDataHandler received a null parameter as a part.WebServicesFault faultCode: {http://schemas.xmlsoap.org/soap/envelope/} Server.generalException faultString: WSWS3250E: Error: AttachmentUtils.getActiviationDataHandler received a null parameter as a part. faultActor: null faultDetail: WSWS3250E: Error: AttachmentUtils.getActiviationDataHandler received a null parameter as a part. at com.ibm.ws.webservices.engine.attachments.AttachmentUtils. getActivationDataHandler(AttachmentUtils.java:125) at com.ibm.ws.webservices.engine.encoding.ser. JAFDataHandlerDeserializer. getDataHandler(JAFDataHandlerDeserializer.java:174) at com.ibm.ws.webservices.engine.encoding.ser. JAFDataHandlerDeserializer. makeValue(JAFDataHandlerDeserializer.java:154) at com.ibm.ws.webservices.engine.encoding. ser.SimpleDeserializer. onEndElement(SimpleDeserializer.java:239) at com.ibm.ws.webservices.engine.encoding.Deserializer. endElement(Deserializer.java:675) ... This can happen on either the client or service. The following is an example of a SOAP message with an Axis-style attachment: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <soapenv:Body> <p935:attachment xmlns:p935="http://example.ibm.com"> <dataHandler href="cid:dataHandler=19620176631.1278648856640.IBM.WEBSERVICES@ examplehost"/> ... ------=_Part_0_1801349982.1278648856656 Content-Type: application/octet-stream Content-Transfer-Encoding: binary Content-Id: <dataHandler=19620176631.1278648856640.IBM.WEBSERVICES@exampleho st> ... The element in the root part (SOAP Envelope) has an href attribute (in the above example, that element is "dataHandler"); the value of the href corresponds to the value of the Content-ID header in the MIME part, which represents the attachment. These characteristics are what make this attachment Axis-style.
Problem conclusion
The JAX-RPC runtime was changed to properly deserialize Axis-style attachments. The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.13. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PM18083
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-07-08
Closed date
2010-07-21
Last modified date
2010-07-21
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R700 PSY
UP
Document Information
Modified date:
24 October 2021