ContributionsMost RecentMost LikesSolutionsRe: ReadyAPI saving/closing/starting the program takes very, very long time Hi, HimanshuTayal really? 40MB are to big?! Never heard that before 😄 Unfortunately it is impossible to split our project into several smaller projects because the tests build on each other and it would get to confusing. That's not an option. So are there any other solutions? Regards, 4nes-team ReadyAPI saving/closing/starting the program takes very, very long time Hi, every time I try to save a 40 MB project (ReadyAPI is installed on a vm and project direrctory is on a external server) it takes meanwhile up to 30 minutes to finish the process. Another issue is the very, very long startup of the program. I tried all the stuff with .vmoptions and by deleting the db content, nothing works. It's like that since approx. version 3.x. Anyone a clue what is wrong with it. I mean we've got an expensive PRO version that's not working properly. Please help. Regards, 4nes-team SolvedREST response without content - closing chunk expected Hi, we are testing a new version of our API but there is no content in the REST response, although the call ran successfully and the action was done in the backround, too (200 status). Also the property 'transfer-encoding=chunked' in the response header is given as it was in the older version of the API, where it was working properly. Nevertheless there is an error log proivided by readyapi, that you maybe could analyze on your side. Thu Jul 08 13:56:57 CEST 2021: ERROR: org.apache.http.ConnectionClosedException: Premature end of chunk coded message body: closing chunk expected org.apache.http.ConnectionClosedException: Premature end of chunk coded message body: closing chunk expected at org.apache.http.impl.io.ChunkedInputStream.getChunkSize(ChunkedInputStream.java:268) at org.apache.http.impl.io.ChunkedInputStream.nextChunk(ChunkedInputStream.java:227) at org.apache.http.impl.io.ChunkedInputStream.read(ChunkedInputStream.java:186) at org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:137) at org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:150) at org.apache.http.util.EntityUtils.toByteArray(EntityUtils.java:136) at org.apache.http.entity.BufferedHttpEntity.<init>(BufferedHttpEntity.java:63) at com.eviware.soapui.impl.wsdl.submit.transports.http.HttpMethodSupport.getResponseBody(HttpMethodSupport.java:236) at com.eviware.soapui.impl.wsdl.submit.transports.http.support.methods.ExtendedPostMethod.getResponseBody(ExtendedPostMethod.java:115) at com.eviware.soapui.impl.wsdl.submit.transports.http.SinglePartHttpResponse.<init>(SinglePartHttpResponse.java:53) at com.eviware.soapui.impl.wsdl.submit.filters.HttpPackagingResponseFilter.httpRequest(HttpPackagingResponseFilter.java:81) at com.eviware.soapui.impl.wsdl.submit.filters.HttpPackagingResponseFilter.afterAbstractHttpResponse(HttpPackagingResponseFilter.java:52) at com.eviware.soapui.impl.wsdl.submit.filters.AbstractRequestFilter.afterRequest(AbstractRequestFilter.java:70) at com.eviware.soapui.impl.wsdl.submit.transports.http.HttpClientRequestTransport.sendRequest(HttpClientRequestTransport.java:295) at com.eviware.soapui.impl.wsdl.WsdlSubmit.run(WsdlSubmit.java:130) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:630) at java.base/java.lang.Thread.run(Thread.java:832) Our development team is currently analyzing this problem on our side, but still maybe you know what could cause this issue. Thanks in advance. Regards, 4nes team. Re: Repeat a test step until desired property value is in the response Hi, is there any possibilty to get an answer to my question? I really hope that there is a solution to my issue. Thanks. Best regards, 4nes team Re: Repeat a test step until desired property value is in the response Hi Aaron, thank you for your quick reply. I tried to implement your code into my testcase but apparently I'm doing something wrong. Could you take a look? You can see the error in the screenshot I attached. Thanks again. 4nes team Repeat a test step until desired property value is in the response Hi, I'm tryin to build a new test step for my API testing, but I don't get the desired result. Below you can see the JSON data from my REST response. So the goal here is to make sure that e.g. at 15pm when the test runs, the JSON response would be checked for the right "reasonCode". In my case it is "EM_004". The response is not always there right on time at 15pm, so that's why I think I need some kind of a loop so I can check for a period of 5 minutes or something like that if the right "reasonCode" is already there. So as soon as the right "reasonCode" is received the loop should stop and the test case should go on. { "id" : "data", "title" : "data", "reasonCode" : "EM_005", "publishedAt" : "data", "reference" : { "productType" : "data", "deliveryDate" : "data", } }, { "id" : "data", "title" : "data", "reasonCode" : "EM_004", "publishedAt" : "data", "reference" : { "productType" : "data", "deliveryDate" : "data", } }, { "id" : "data", "title" : "data", "reasonCode" : "EM_002", "publishedAt" : "data", "reference" : { "productType" : "data", "deliveryDate" : "data", } } Unfortunately I'm a total noob at groovy-scripting and stuff like that so it would be very cool if you could help me out here. If there are any further question just write me a pm or direct response, please. Thanks a lot in advance, 4nes team