A fix is available
APAR status
Closed as program error.
Error description
When a web service request comes in and specifies a charset of iso-8859-1 when an inputstream has already been created using UTF-8, the following exception will be seen: . WSWS3227E: Error: Exception:java.lang.Exception: WSWS3710E: Internal Error: Attempt to change encoding on WebServicesInputSource from utf-8 to iso-8859-1. at com.ibm.ws.webservices.engine.InternalException.<init>(InternalE xception.java:124) at com.ibm.ws.webservices.utils.WebServicesInputSource.setEncoding( WebServicesInputSource.java:197) at com.ibm.ws.webservices.engine.SOAPPart._getSOAPEnvelope(SOAPPart .java:1027) ...
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of WebSphere Application Server * * V7.0 JAX-RPC web service clients * * and providers that receive messages in * * ISO-8859-1 character encoding. * * * **************************************************************** * PROBLEM DESCRIPTION: A message in ISO-8859-1 encoding might * * be rejected by the WebSphere * * Application Server web services * * JAX-RPC runtime. * * * **************************************************************** * RECOMMENDATION: * **************************************************************** A web services client might send a request in ISO-8859-1 character encoding to a WebSphere Application Server web service. In this case, the user might observe this on the service side: WSWS3227E: Error: Exception:java.lang.Exception: WSWS3710E: Internal Error: Attempt to change encoding on WebServicesInputSource from utf-8 to iso-8859-1. at com.ibm.ws.webservices.engine.InternalException.<init>(InternalE xception.java:124) at com.ibm.ws.webservices.utils.WebServicesInputSource.setEncoding( WebServicesInputSource.java:197) ... The client might receive a SOAP Fault like the 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/> <soapenv:Body> <soapenv:Fault xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> <faultcode>soapenv:Server.generalException</faultcode> <faultstring>WSWS3400I: Info: unexpected exception. </faultstring> </soapenv:Fault> </soapenv:Body> </soapenv:Envelope> Similarly, the WSWS3710E InternalException might also occur on a WebSphere Application Server client if it receives a response in ISO-8859-1 encoding.
Problem conclusion
The V6.1 JAX-RPC web services code was changed to tolerate ISO-8859-1 character encoding. Note that the SAAJ 1.2 and 1.3 specifications require only UTF-8 and UTF-16. APAR PK82643 is currently targeted for inclusion in Service Level (Fix Pack) 7.0.0.3 of WebSphere Application Server V7.0. Please refer to URL: //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970 for Fix Pack availability.
Temporary fix
Comments
APAR Information
APAR number
PK82643
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-03-16
Closed date
2009-03-19
Last modified date
2009-05-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
BBGUBINF BBOUBINF
Fix information
Fixed component name
WEBSPHERE FOR Z
Fixed component ID
5655I3500
Applicable component levels
R700 PSY UK45160
UP09/04/06 P F904
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
10 February 2022