Soap Fault Issue

Question

I think this is more likely a Websphere problem we are having than a loadUI Pro issue, but wanted to know if you have any issues with load tests that generate a lot of soap faults versus normal responses. The behavior we get is that the connection is being refused by the server. It happens at low volume (1/s with burst of 5). The same web service has no failures when processed as a normal response. Our goal is to just eliminate the client as a possible issue, which we see as very unlikely. I did edit out the name of our server.

Here is the trace:
2013-07-29 16:14:24,772 ERROR [errorlog] org.apache.http.conn.HttpHostConnectException: Connection to https://servername refused
org.apache.http.conn.HttpHostConnectException: Connection to https://servername refused
at com.eviware.soapui.impl.wsdl.support.http.SoapUIMultiThreadedHttpConnectionManager$SoapUIClientConnectionOperator.openConnection(SoapUIMultiThreadedHttpConnectionManager.java:321)
at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:149)
at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:121)
at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:561)
at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:415)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:820)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:754)
at com.eviware.soapui.impl.wsdl.support.http.HttpClientSupport$Helper.execute(HttpClientSupport.java:246)
at com.eviware.soapui.impl.wsdl.support.http.HttpClientSupport.execute(HttpClientSupport.java:356)
at com.eviware.soapui.impl.wsdl.submit.transports.http.HttpClientRequestTransport.sendRequest(HttpClientRequestTransport.java:234)
at com.eviware.soapui.impl.wsdl.WsdlSubmit.run(WsdlSubmit.java:123)
at com.eviware.soapui.impl.wsdl.WsdlSubmit.submitRequest(WsdlSubmit.java:76)
at com.eviware.soapui.impl.wsdl.WsdlRequest.submit(WsdlRequest.java:238)
at com.eviware.soapui.impl.wsdl.teststeps.WsdlTestRequestStep.run(WsdlTestRequestStep.java:417)
at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.runTestStep(AbstractTestCaseRunner.java:239)
at com.eviware.soapui.impl.wsdl.testcase.WsdlTestCaseRunner.runCurrentTestStep(WsdlTestCaseRunner.java:48)
at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.internalRun(AbstractTestCaseRunner.java:148)
at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.internalRun(AbstractTestCaseRunner.java:43)
at com.eviware.soapui.impl.wsdl.support.AbstractTestRunner.run(AbstractTestRunner.java:135)
at com.eviware.loadui.components.soapui.SoapUISamplerComponent$SoapUITestCaseRunner.run(SoapUISamplerComponent.java:756)
at com.eviware.loadui.components.soapui.SoapUISamplerComponent.sample(SoapUISamplerComponent.java:597)
at com.eviware.loadui.impl.component.categories.RunnerBase.doSample(RunnerBase.java:489)
at com.eviware.loadui.impl.component.categories.RunnerBase.access$700(RunnerBase.java:58)
at com.eviware.loadui.impl.component.categories.RunnerBase$Worker.run(RunnerBase.java:749)
at com.eviware.loadui.util.dispatch.CustomThreadPoolExecutor$Worker.run(CustomThreadPoolExecutor.java:197)
at java.lang.Thread.run(Unknown Source)
Caused by: java.net.ConnectException: Connection timed out: connect
at java.net.DualStackPlainSocketImpl.connect0(Native Method)
at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)
at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at sun.security.ssl.SSLSocketImpl.connect(Unknown Source)
at com.eviware.soapui.impl.wsdl.support.http.SoapUISSLSocketFactory.connectSocket(SoapUISSLSocketFactory.java:218)
at com.eviware.soapui.impl.wsdl.support.http.SoapUIMultiThreadedHttpConnectionManager$SoapUIClientConnectionOperator.openConnection(SoapUIMultiThreadedHttpConnectionManager.java:299)
... 25 more

smartbear_suppo · Answer

Hi,This is not something that we've had any issues with in the past. Hopefully you'll be able to figure out the root cause quickly.Let me know if you have any other questions and we'll happily assist.Regards,ArianSmartBear Sweden

nicholasglen · Answer

Please refer to open/close connection issue in this forum. This does appear to be a loadui/soapui issue as it closes the connection when a fault occurs. A fault return http 500 as a matter of standard, but a fault can indicate normal processing as well as exceptions. When a high number of faults occur the dropping of the connection causes the server to have issues with to many connections. This problem can be recreated with as few as 5 tps burst against a production configured WebSphere instance. A custom java client we wrote with multiple threads does not cause this to break. If there is a way to not have a http 500 drop the connection with a soap fault that would likely resolve the issue.
soap UI raw response. http 500 is the expected response for a soap fault, but dropping a connection is up to the client.

HTTP/1.1 500 Internal Server Error
X-Powered-By: Servlet/3.0
Content-Type: text/xml; charset=UTF-8
Content-Language: en-US
Content-Length: 1028
Connection: Close
Date: Wed, 04 Sep 2013 18:56:47 GMT

<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><soapenv:Fault><faultcode>soapenv:Server</faultcode><faultstring>Both MEDS ID and Person SSN cannot be specified. One or the other must be specified.</faultstring><detail><d:ValidationFault xmlns:a="http://dhcs.ca.gov/services/header" xmlns:b="http://dhcs.ca.gov/core/location" xmlns:c="http://niem.gov/niem/structures/2.0" xmlns:d="http://dhcs.ca.gov/services/fault" xmlns:e="http://dhcs.ca.gov/services/eligibility" xmlns:f="http://dhcs.ca.gov/core/member" xmlns:g="http://niem.gov/niem/domains/immigration/2.1" xmlns:h="http://dhcs.ca.gov/core/eligibility" xmlns:i="http://dhcs.ca.gov/core/application" xmlns:j="http://dhcs.ca.gov/core/common" xmlns="http://niem.gov/niem/niem-core/2.0"><d:message>Both MEDS ID and Person SSN cannot be specified. One or the other must be specified.</d:message><d:code>25002</d:code></d:ValidationFault></detail></soapenv:Fault></soapenv:Body></soapenv:Envelope>

smartbear_suppo · Answer

Hi Nicholas,Please try my suggestion in the other post and let us know if that helps.Regards,RenatoSmartBear Software

Forum Discussion

Soap Fault Issue

Related Content

SOAP Fault Vs Not SOAP Fault

Issue Coverage

SOAP UI API Docs

Soap ui

SOAP Response timeout

Recent Discussions

Accessing database connection string from groovy test step

Best Practices for Testing HTTP/2 Steps

Include external files (XML) for JDBC connection

Assert Step Not Executing All Assertions

JDBC database connection pooling