APAR status
Closed as program error.
Error description
Using customer supplied ear file on WSAS 5.02 server configured
to use Active Directory as the LDAP server. Using the correct
user and password: Result: Test12345
Using incorrect name: javax.xml.soap.SOAPException: WSEC5078E:
Login failed:
com.ibm.websphere.security.auth.WSLoginFailedException: No user
xxxxxx found at
com.ibm.ws.webservices.engine.soap.SOAPConnectionImpl.call(SOAPC
onnectionImpl.java:115)
at test.ClientwithSoapHdr.main(ClientwithSoapHdr.java:83)
Using incorrect password:
javax.xml.soap.SOAPException: org.xml.sax.SAXParseException: An
invalid XML character (Unicode: 0x0) was found in the CDATA
section. at
com.ibm.ws.webservices.engine.soap.SOAPConnectionImpl.call(SOAPC
onnectionImpl.java:115)
at test.ClientwithSoapHdr.main(ClientwithSoapHdr.java:83)
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All WebSphere Application Server users. *
****************************************************************
* PROBLEM DESCRIPTION: Invalid character inside of CDATA *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When an exception is thrown in a customer's web service, the
SOAPFaultException is wrapped with a WebServicesFault and
then returned to the user. The faultString element
of that WSFault is wrapped in a CDATA section with the
error message returned by the application.
The problem arises when there are characters returned in the
message that do not belong in a CDATA section.
Problem conclusion
To fix this, we removed the CDATA wrapper from around the
faultString element.
Temporary fix Comments
APAR information |
APAR number |
PQ90673 |
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 |
2004-06-25 |
Closed date |
2004-07-19 |
Last modified date |
2004-07-19 |
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 |
|