APAR status
Closed as program error.
Error description
The apar should be routed to webservices component.
WebSphere Portal Server(WPS) v5.0.2.2 & 5.1 are not able to
consume a PeopleSoft portlet using WSRP services, and throws a
SOAP deserializer error.
Error Message in WPS:
<?xml version="1.0" encoding="utf-8"?>
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Server.userException</faultcode>
<faultstring>org.xml.sax.SAXException: No deserializer for
{http://schemas.xmlsoap.org/soap/encoding/}boolean</faultstring>
<detail/>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
The Peoplesoft WSRP will work only if we have a JSR
remote portlet running on the WPS consumer box. It seems like
JSR loads some jar files which seem to help the WSRP/webservices
After analyzing the test case provided it was
determined that a combination of a normally benign
serialization Java code generation defect and a performance
improvement algorithm resulted in the customer's issue of
adding an incorrect namespace specifically with Apache Axis.
Local fix
The Peoplesoft WSRP will work only if we have a JSR
remote portlet running on the WPS consumer box.
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users of web *
* services *
****************************************************************
* PROBLEM DESCRIPTION: SOAP Deserializer Error *
****************************************************************
* RECOMMENDATION: *
****************************************************************
WebSphere Portal Server(WPS) v5.0.2.2 & 5.1 are not able to
consume a PeopleSoft portlet using WSRP services, and throws a
SOAP deserializer error.
Error Message in WPS:
<?xml version="1.0" encoding="utf-8"?>
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Server.userException</faultcode>
<faultstring>org.xml.sax.SAXException: No deserializer for
{http://schemas.xmlsoap.org/soap/encoding/}boolean</faultstring>
<detail/>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
After analyzing the test case provided it was determined that a
combination of a normally benign serialization Java code
generation defect and a performance improvement algorithm
resulted in the issue of adding an incorrect namespace
specifically with Apache Axis.
Problem conclusion
Fixed serialization error.
The fix for this APAR is currently targeted for inclusion in
fixpack 5.0.2.11 and 5.1.1.4. Please refer to the Recommended
Updates page for delivery dates:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix Comments
APAR information |
APAR number |
PQ99864 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A3600 |
Reported release |
00W |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2005-01-21 |
Closed date |
2005-03-04 |
Last modified date |
2005-03-04 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
Applicable component levels |
R003 PSY |
UP |
R00A PSY |
UP |
R00H PSY |
UP |
R00I PSY |
UP |
R00P PSY |
UP |
R00S PSY |
UP |
R00W PSY |
UP |
R103 PSY |
UP |
R10A PSY |
UP |
R10H PSY |
UP |
R10I PSY |
UP |
R10P PSY |
UP |
R10S PSY |
UP |
R10W PSY |
UP |
|