PK40114: WSWS3228E with a misleading java.lang.NumberFormatException due to xmlns mismatch between wsdl file and SOAP request

Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR10 Cumulative Fix for WebSphere Application Server
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
6.1.0.9: WebSphere Application Server V6.1 Fix Pack 9 for Solaris

APAR status

• Closed as program error.

Error description

• The WSDL used to generate the client and endpoint has
  xmlns:xsd="http://www.w3.org/2001/XMLSchema"
  
  but the SOAP request sent contains:
  xmlns:xsd="http://www.w3.org/1999/XMLSchema">
  
  There is a mis-match in the year in the URLs.
  
  This results in a NumberFormatException, which is misleading
  [2/8/07 11:36:19:572 EST] 0000002a UserException E   WSWS3228E:
  Error:
  Exception: WebServicesFault
   faultCode:
  {http://schemas.xmlsoap.org/soap/envelope/}Server.generalExcepti
  on
   faultString: java.lang.NumberFormatException: For input string:
  "" Message being parsed:
   faultActor: null
   faultDetail:
  
  java.lang.NumberFormatException: For input string: "" Message
  being parsed:
   at
  com.ibm.ws.webservices.engine.WebServicesFault.makeFault(WebServ
  icesFault.java:206)
   at
  com.ibm.ws.webservices.engine.SOAPPart._getSOAPEnvelope(SOAPPart
  .java:1062)
   ...
  
  Caused by: java.lang.NumberFormatException: For input string: ""
   at
  java.lang.NumberFormatException.forInputString(NumberFormatExcep
  tion.java:63)
   at java.lang.Integer.parseInt(Integer.java:502)
   at java.lang.Short.parseShort(Short.java:135)
   at java.lang.Short.(Short.java:346)
   at
  com.ibm.ws.webservices.engine.encoding.ser.SimpleDeserializer.pa
  rseShort(SimpleDeserializer.java:455)
   at
  com.siemens.soarian.se.alert.data.v1.CreateRequestType_Deser.try
  ElementSetFromString(CreateRequestType_Deser.java:35)
   at
  com.ibm.ws.webservices.engine.encoding.ser.BeanDeserializer.onSi
  mpleChild(BeanDeserializer.java:586)
   at
  com.ibm.ws.webservices.engine.events.P2DConverter.flush(P2DConve
  rter.java:771)
   at
  com.ibm.ws.webservices.engine.events.P2DConverter.endElement(P2D
  Converter.java:414)
   at
  com.ibm.xml.xlxp.api.sax.impl.SAX2ParserBase.startElementAction(
  SAX2ParserBase.java:234)
  

Local fix

• Correct the WebServices client so that the xmlns tag it includes
  has a date that matches the one in the wsdl file.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: WebSphere Application Server version 6.1     *
  *                 users of Web Services                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: Using xsi:nil='true' with a schema      *
  *                      that does support xsi:nil results in a  *
  *                      NumberFormatException, which is         *
  *                      misleading                              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When using a WSDL that has
  
  xmlns:xsd="http://www.w3.org/2001/XMLSchema"
  
  client has this in the SOAP request:
  
  xmlns:xsd="http://www.w3.org/1999/XMLSchema">
  
  There is a mis-match in the year in the URLs. This results in
  a NumberFormatException, which is misleading.
  

Problem conclusion

• We should not have attempted to deserialze an empty string,
  that was causing the NumberFormatException.  The change was to
  test for the empty string and return without attempting to
  deserialize it.
  
  This fix is targeted for fixpack 6.1.0.9.
  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 is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

• WEBSRVC
  

Fix information

• Fixed component name

  WEBSPH APP SERV

• Fixed component ID

  5724J0800

Applicable component levels

• R60A PSN

     UP

• R60H PSN

     UP

• R60I PSN

     UP

• R60P PSN

     UP

• R60S PSN

     UP

• R60W PSN

     UP

• R60Z PSN

     UP

• R61A PSY

     UP

• R61H PSY

     UP

• R61I PSY

     UP

• R61P PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP

• R61Z PSY

     UP