APAR status
Closed as program error.
Error description
Feature Pack for Web Services enabled thin client running inside Application Server Toolkit(AST) as a JUNIT test client gets a NullPointerException while parsing the message from the WebSphere Application Server. ------------------------------- May 2, 2008 12:32:55 PM org.apache.axis2.jaxws.message.databinding.JAXBUtils getJAXBUnmarshaller FINE: Unmarshaller created [no pooling] May 2, 2008 12:32:55 PM org.apache.axis2.jaxws.message.databinding.impl.JAXBBlockImpl _getBOFromReader FINE: Adding JAXBAttachmentUnmarshaller to Unmarshaller May 2, 2008 12:32:55 PM org.apache.axis2.jaxws.message.databinding.impl.JAXBBlockImpl unmarshalByType FINE: Invoking unmarshalByType. May 2, 2008 12:32:55 PM org.apache.axis2.jaxws.message.attachments.JAXBAttachmentUnmarsh aller isXOPPackage FINE: isXOPPackage returns true May 2, 2008 12:32:55 PM org.apache.axis2.jaxws.ExceptionFactory logRootCause FINE: Root Cause:javax.xml.bind.UnmarshalException - with linked exception: [java.lang.NullPointerException] May 2, 2008 12:32:55 PM org.apache.axis2.jaxws.ExceptionFactory logRootCause FINE: stack:javax.xml.bind.UnmarshalException - with linked exception: [java.lang.NullPointerException] at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.handle StreamException(UnmarshallerImpl.java:417) at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmars hal0(UnmarshallerImpl.java:342) at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmars hal(UnmarshallerImpl.java:319) at org.apache.axis2.jaxws.message.databinding.impl.JAXBBlockImpl$4. run(JAXBBlockImpl.java:513) at org.apache.axis2.java.security.AccessController.doPrivileged(Acc essController.java:74) at org.apache.axis2.jaxws.message.databinding.impl.JAXBBlockImpl.un marshalByType(JAXBBlockImpl.java:439) at org.apache.axis2.jaxws.message.databinding.impl.JAXBBlockImpl._g etBOFromReader(JAXBBlockImpl.java:133) Caused by: java.lang.NullPointerException at org.apache.xml.utils.DOMBuilder.startElement(DOMBuilder.java:413 ) at org.apache.xalan.transformer.TransformerIdentityImpl.startElemen t(TransformerIdentityImpl.java:1093) at com.sun.xml.bind.v2.runtime.unmarshaller.DomLoader.startElement( DomLoader.java:82) at com.sun.xml.bind.v2.runtime.unmarshaller.ProxyLoader.startElemen t(ProxyLoader.java:19) at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallingContext._s tartElement(UnmarshallingContext.java:369) at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallingContext.st artElement(UnmarshallingContext.java:347) at com.sun.xml.bind.v2.runtime.unmarshaller.MTOMDecorator.startElem ent(MTOMDecorator.java:71) at com.sun.xml.bind.v2.runtime.unmarshaller.InterningXmlVisitor.sta rtElement(InterningXmlVisitor.java:35) at com.sun.xml.bind.v2.runtime.unmarshaller.StAXStreamConnector.han dleStartElement(StAXStreamConnector.java:224) at com.sun.xml.bind.v2.runtime.unmarshaller.StAXStreamConnector.bri dge(StAXStreamConnector.java:158) at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmars hal0(UnmarshallerImpl.java:340) ... 38 more ------------------------------------------------- The SOAP message being parsed is below. ======================================= <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:Header> <TEAM:header xmlns:TEAM="http://xmlns.rational.com/TEAM"> <TEAM:session-key>62b8310049920a41adeaffe547aaa29c</TEAM:session -key> <TEAM:session-timeout>1800</TEAM:session-timeout> </TEAM:header> </soapenv:Header> <soapenv:Body> <p692:property-reportResponse xmlns:p692="http://stp.rational.ibm.com/ws/teamservice"> <body xmlns:WSX="http://stp.rational.ibm.com/ws/schema" xmlns:TEAM="http://xmlns.rational.com/TEAM" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <WSX:property-report> <WSX:resource>cq.repo.cq-userdb:@CQWAN/CQWAN</WSX:resource> <WSX:propstat> <WSX:name-values> <WSX:value WSX:property="TEAM:product-info" WSX:type="XML"> <WSX:content xsi:type="WSX:XmlDoc" xmlns:TEAM="http://xmlns.rational.com/TEAM" xmlns:CQ="http://xmlns.rational.com/TEAM/CQ"> <TEAM:build-number>00295</TEAM:build-number> <TEAM:company-email-address>us.ibm.com</TEAM:company-email-addre ss> <TEAM:company-full-name>IBM Corporation</TEAM:company-full-name> <TEAM:company-name>IBM</TEAM:company-name> <TEAM:company-web-address>www.ibm.com</TEAM:company-web-address> <CQ:default-dbset-name>Default</CQ:default-dbset-name> <TEAM:full-product-version>7.1.0.0</TEAM:full-product-version> <CQ:obj-model-version CQ:obj-model-version-major="1" CQ:obj-model-version-minor="8"/> <TEAM:patch-version>0.0</TEAM:patch-version> <TEAM:product-version>7.0.0</TEAM:product-version> <TEAM:stage-label>7.1.D080313</TEAM:stage-label> </WSX:content> </WSX:value> </WSX:name-values> </WSX:propstat> </WSX:property-report> </body> </p692:property-reportResponse> </soapenv:Body> </soapenv:Envelope> =========================================== Note that the <WSX:content> element has a xsi:type="WSX:XmlDoc" attribute, which forces the JAXB unmarshaller to use the XML Schema. The difference between the fails and succeeds message is that in the case of fails the embedded <CQ:obj-model-version> element has XML attributes.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server Feature Pack for Web Services * **************************************************************** * PROBLEM DESCRIPTION: NullPointerException in Feature * * Pack for Web Services enabled thin * * client inside Application Server * * Toolkit * **************************************************************** * RECOMMENDATION: * **************************************************************** Feature Pack for Web Services enabled thin client running inside Application Server Toolkit as a JUNIT test client gets a NullPointerException while parsing the message from the WebSphere Application Server. This problem happened because the attribute type was not being stored.
Problem conclusion
The attribute type was not being stored, added logic to store the attribute type. The fix for this APAR is currently targeted for inclusion in fixpack 6.1.0.19. 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
PK66502
Reported component name
WEBSERVIC FEATU
Reported component ID
5724J0850
Reported release
610
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-05-22
Closed date
2008-06-06
Last modified date
2008-06-06
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
WEBSERVIC FEATU
Fixed component ID
5724J0850
Applicable component levels
R610 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
10 February 2022