Forum Discussion
SmartBear_Suppo
11 years agoSmartBear Alumni (Retired)
Hi,
Sorry about the confusion. Reading the whole thread it's quite clear to me that this is not a proxy issue, although it was a good guess until you gave us all the information.
The stale connection check is performed by a third party library - Apache HTTP Client. It is possible to turn it off, but it seems that you can only do it programmatically (by changing the code) and not by configuration. However, I looked at the source code of Apache HTTP Client, and the log statement you're seeing occurs *before* the stale connection check. In other words, something else is causing the delay, and we need to find out what.
This would be much easier for us if we could reproduce your problem in the development team. There must be something unusual going on in the interaction between SoapUI and your REST service, but at the moment we have no good guess what it is. Is the service you're testing available online, or could you make it available temporarily and share your project file with us, so we can make a serious attempt to reproduce the delays.
I think you'd better open a support ticket, so you can share as much information about the REST service and test scenarios as possible. As you probably know the form to open a ticket is on this page: http://www.soapui.org/Support/support-overview.html.
Kind regards,
Manne
Sorry about the confusion. Reading the whole thread it's quite clear to me that this is not a proxy issue, although it was a good guess until you gave us all the information.
The stale connection check is performed by a third party library - Apache HTTP Client. It is possible to turn it off, but it seems that you can only do it programmatically (by changing the code) and not by configuration. However, I looked at the source code of Apache HTTP Client, and the log statement you're seeing occurs *before* the stale connection check. In other words, something else is causing the delay, and we need to find out what.
This would be much easier for us if we could reproduce your problem in the development team. There must be something unusual going on in the interaction between SoapUI and your REST service, but at the moment we have no good guess what it is. Is the service you're testing available online, or could you make it available temporarily and share your project file with us, so we can make a serious attempt to reproduce the delays.
I think you'd better open a support ticket, so you can share as much information about the REST service and test scenarios as possible. As you probably know the form to open a ticket is on this page: http://www.soapui.org/Support/support-overview.html.
Kind regards,
Manne
Related Content
Recent Discussions
- 6 days agogroovyguy