SoapUIMultiThreadedHttpConnectionManager Connection closed
Hello,
I need help with a randomly experienced issue/problem (might be an intermittent bug/defect). I'm running SoapUI Test Suites through maven and 4.6.1 SoapUI Maven plugin. This test execution is triggered via a Jenkins job.
Please see a pom.xml excerpt:
......
<pluginRepository>
<id>smartbear-sweden-plugin-repository</id>
<url>http://www.soapui.org/repository/maven2/</url>
</pluginRepository>
......
......
<groupId>com.smartbear.soapui</groupId>
<artifactId>soapui-maven-plugin</artifactId>
<version>4.6.1</version>
......
Some of these test cases send requests to an asynchronous web service. The responses in these cases are received in SoapUI within Mock Response test steps configured to listen on, for example /PartyEBFResponseBinding/AddOrgResponse port 8001. The thing is that most of the times the test execution jams/stops at this point with the following Jenkins log message:
12:07:14 12:07:24,418 INFO [WsdlMockRunner] Mounted WSDL for interface [PartyEBFResponseBinding] at [/PartyEBFResponseBinding/AddOrgResponse?WSDL]
12:07:14 12:07:24,586 INFO [JettyMockEngine] Started mockService [Mock AddOrgResponse] on port [8001] at path [/PartyEBFResponseBinding/AddOrgResponse]
12:07:39 12:07:49,307 DEBUG [SoapUIMultiThreadedHttpConnectionManager$SoapUIDefaultClientConnection] Connection closed
The fault details on server side, seen in OEM (Oracle Enterprise Manager), specify that:
Non Recoverable System Fault :
<bpelFault><faultType>0</faultType><remoteFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="summary"><summary>oracle.fabric.common.FabricInvocationException: Unable to invoke endpoint URI "http://10.168.41.126:8001/PartyEBFResponseBinding/AddOrgResponse" successfully due to: javax.xml.soap.SOAPException: javax.xml.soap.SOAPException: Message send failed: Connection refused</summary></part><part name="detail"><detail>Unable to invoke endpoint URI "http://10.168.41.126:8001/PartyEBFResponseBinding/AddOrgResponse" successfully due to: javax.xml.soap.SOAPException: javax.xml.soap.SOAPException: Message send failed: Connection refused</detail></part><part name="code"><code>null</code></part></remoteFault></bpelFault>
It seems like the remote machine on which these tests run refuses the connection.
This test execution sometimes runs smoothly till the end without jamming, sometimes meaning (as I've noticed) once a day, i.e the first run. Subsequent runs jam. Out of 10 runs a day, 9 fail I would say.
I've attached two log files: one log shows the success scenario and the other one displays the logs collected till the test run blocks and the connection is closed.
Did anyone encounter this behavior/issue before? Is it a configuration mistake that I did or is this a known issue?
Note: All these test suites run perfectly when I’m not using maven and the Jenkins job, that is, running them locally on the remote machine from SoapUI with TestRunner.
Please tell me if you need additional details in order to investigate. I need to find a solution or an workaround as soon as possible as these suites need to be executed at any hour by triggering the Jenkins job.
Thank you very much,
Lucian
I need help with a randomly experienced issue/problem (might be an intermittent bug/defect). I'm running SoapUI Test Suites through maven and 4.6.1 SoapUI Maven plugin. This test execution is triggered via a Jenkins job.
Please see a pom.xml excerpt:
......
<pluginRepository>
<id>smartbear-sweden-plugin-repository</id>
<url>http://www.soapui.org/repository/maven2/</url>
</pluginRepository>
......
......
<groupId>com.smartbear.soapui</groupId>
<artifactId>soapui-maven-plugin</artifactId>
<version>4.6.1</version>
......
Some of these test cases send requests to an asynchronous web service. The responses in these cases are received in SoapUI within Mock Response test steps configured to listen on, for example /PartyEBFResponseBinding/AddOrgResponse port 8001. The thing is that most of the times the test execution jams/stops at this point with the following Jenkins log message:
12:07:14 12:07:24,418 INFO [WsdlMockRunner] Mounted WSDL for interface [PartyEBFResponseBinding] at [/PartyEBFResponseBinding/AddOrgResponse?WSDL]
12:07:14 12:07:24,586 INFO [JettyMockEngine] Started mockService [Mock AddOrgResponse] on port [8001] at path [/PartyEBFResponseBinding/AddOrgResponse]
12:07:39 12:07:49,307 DEBUG [SoapUIMultiThreadedHttpConnectionManager$SoapUIDefaultClientConnection] Connection closed
The fault details on server side, seen in OEM (Oracle Enterprise Manager), specify that:
Non Recoverable System Fault :
<bpelFault><faultType>0</faultType><remoteFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="summary"><summary>oracle.fabric.common.FabricInvocationException: Unable to invoke endpoint URI "http://10.168.41.126:8001/PartyEBFResponseBinding/AddOrgResponse" successfully due to: javax.xml.soap.SOAPException: javax.xml.soap.SOAPException: Message send failed: Connection refused</summary></part><part name="detail"><detail>Unable to invoke endpoint URI "http://10.168.41.126:8001/PartyEBFResponseBinding/AddOrgResponse" successfully due to: javax.xml.soap.SOAPException: javax.xml.soap.SOAPException: Message send failed: Connection refused</detail></part><part name="code"><code>null</code></part></remoteFault></bpelFault>
It seems like the remote machine on which these tests run refuses the connection.
This test execution sometimes runs smoothly till the end without jamming, sometimes meaning (as I've noticed) once a day, i.e the first run. Subsequent runs jam. Out of 10 runs a day, 9 fail I would say.
I've attached two log files: one log shows the success scenario and the other one displays the logs collected till the test run blocks and the connection is closed.
Did anyone encounter this behavior/issue before? Is it a configuration mistake that I did or is this a known issue?
Note: All these test suites run perfectly when I’m not using maven and the Jenkins job, that is, running them locally on the remote machine from SoapUI with TestRunner.
Please tell me if you need additional details in order to investigate. I need to find a solution or an workaround as soon as possible as these suites need to be executed at any hour by triggering the Jenkins job.
Thank you very much,
Lucian
