SOAPException: faultCode=SOAP-ENV:Client; msg=For input string: "3773 "; targetException=java.lang.NumberFormatException ~ foundjava

I get this warning with JMeter

WARN - jmeter.protocol.http.sampler.WebServiceSampler: [SOAPException: faultCode=SOAP-ENV:Client; msg=For input string: "3773 "; targetException=java.lang.NumberFormatException: For input string: "3773 "]

every time I try to test a web service by running a WebService(SOAP) Request. Strange it might seem, but I found out that the error is actually a network error; to be more specific an HTTP/1.1 504 Proxy Timeout ( The connection timed out. ). The original error is totally misleading.

The connection times out, so I get no SOAP response back. What I get though is the headers, the content and the content length back. But for some reason the content length is padded with some spaces at the end and when the HTTPUtils (the class that handles the SOAP request/response) tries to parse it with this statement

Integer.parseInt(value);

it fails. I had to rebuild jmeter and step through it with breakpoints in order to see what’s going on. The solution is as simple as adding a trim to the statement (a couple of lines above the offending statement):

String value = valuebuf.toString().trim();

This fixes the issue and you get the actual response back which is

Error Code 10060: The gateway could not receive a timely response from the website you are trying to access. This might indicate that the network is congested, or that the website is experiencing technical difficulties..

Read More »

[wsdlc] [ERROR] A class/interface with the same name “com.mydomain.layer.inbound.ws.ValidateResponse” is already in use. Use a class customizat ion to resolve this conflict. ~ foundjava

I got the error [wsdlc] [ERROR] A class/interface with the same name "com.mydomain.layer.inbound.ws.ValidateResponse" is already in use. Use a class customization to resolve this conflict. a few days ago when I tried to generate the Java code from a WSDL file, using Oracle’s wsdlc Ant task. The problem is caused by having two elements with the same name, but with a different namespace, in the WSDL file. For example the following bit of code will result in the error above:

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18

<s:element name="ValidateResponse">         <s:complexType>           <s:sequence>             <s:element minOccurs="0" maxOccurs="1" name="ValidateResult" type="tns:ValidateResponse" />           </s:sequence>         </s:complexType>       </s:element>       <s:complexType name="ValidateResponse">         <s:complexContent mixed="false">           <s:extension base="tns:Response">             <s:sequence>               <s:element minOccurs="1" maxOccurs="1" name="Status" type="tns:ResponseStatus" />               <s:element minOccurs="0" maxOccurs="1" name="SubscriptionExpiry" type="s:string" />               <s:element minOccurs="0" maxOccurs="1" name="Allowed" type="tns:ArrayOfGuid" />             </s:sequence>           </s:extension>         </s:complexContent>       </s:complexType>

The solution to this is to use a JAXB Customisation Binding, as explained here. By using a JAXB Customisation Binding you can essentially bind a WSDL element to another type and therefore resolve the conflict, since in the generated Java code you end up with two different artifacts.

There are two ways do it. The first one is to use an external JAXB Customisation Binding file. Unfortunately this solution did not work for me. Not sure what the problem was. The second solution is to use inline JAXB Customisation Binding code. Fortunately this solution did work for me. By inlining the JAXB binding you end up with the following bit of code

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23

<s:element name="ValidateResponse">         <s:complexType>           <s:sequence>             <s:element minOccurs="0" maxOccurs="1" name="ValidateResult" type="tns:ValidateResponse" />           </s:sequence>         </s:complexType>       </s:element>       <s:complexType name="ValidateResponse">         <s:annotation>           <s:appinfo>             <jaxb:class name="ValidateResponseComplexType"/>           </s:appinfo>         </s:annotation>       <s:complexContent mixed="false">         <s:extension base="tns:Response">           <s:sequence>             <s:element minOccurs="1" maxOccurs="1" name="Status" type="tns:ResponseStatus" />             <s:element minOccurs="0" maxOccurs="1" name="SubscriptionExpiry" type="s:string" />             <s:element minOccurs="0" maxOccurs="1" name="Allowed" type="tns:ArrayOfGuid" />           </s:sequence>         </s:extension>       </s:complexContent>       </s:complexType>

When the wsdlc runs you will end up with the different classes for the ValidateResponse element: ValidateResponse and ValidateResponseComplexType. Of course you will also need to define the jaxb namespace: xmlns:jaxb="http://java.sun.com/xml/ns/jaxb" in the WSDL file.

Read More »