ContributionsMost RecentMost LikesSolutionsRe: Failed to init connection - Postgres Ah - There is a typo on the SoapUI documentation site. Adding the 'j' fixed the issue; Re: Failed to init connection - Postgres Hi Shashavali - have tried that but unfortunately get the same error. The Postgres driver I've downloaded is for Java 8, is that the correct version for SoapUI 5.6.0? Failed to init connection - Postgres Hello, I'm receiving the below error when attempting to create a connection to a postgres database running SoapUI version 5.6.0 I have copied the postgresql-42.5.1.jar file to the below location; C:\Program Files\SmartBear\SoapUI-5.6.0\bin\ext I've tried restarting SoapUI to no avail. Could someone please advise what I may be doing wrong? SolvedZepher Testcase Importer Hi, I'm having an issue when running the test case importer. I can connect to the JIRA instance without issue, and select the project from the returned list, however the tool just hangs when I select any of the Issue Types (please see attached screenshot). I'm using Zepher for JIRA 4.1.2 SoapUI - Run primary Test case (wait for running to finish, Thread safe) Is it possible to call a test case in groovy and set the property 'Run primary Test case (wait for running to finish, Thread safe)' Normally this option would be set by checking the flag in a 'Run test case' script, however when calling a test case from a Mock Service dispatch script this is not possible. Is there a way around this? Many thanks. SoapUI - Mock Response times I am running a Mock Service which is running several different Mock Operations. What I am finding however that the logged response times are taking several seconds, which seems a long time. If I eyeball the raw messages, they seem to be created instantly. I have also put timers in the dispatch script code which shows there are no delay there (the code runs in milliseconds). Can somebody please advise if the logged response times in the Mock Operations log is purely the time it took to generate the response, or if this includes the network comms – i.e. that the response time includes sending the response back to the app? I’m struggling to pinpoint where the delay is. Many thanks in advance Mock service - java.lang.IndexOutOfBoundsException Hi, I am running a Mock Service which is running several different Mock Operations. When running at heavy load (several requests per second into the Mock Service), every 20 minutes or so I get the following error; ERROR: com.eviware.soapui.impl.wsdl.mock.DispatchException:java.lang.IndexOutOfBoundsException:Index: 1, Size:1 There are no scripts involved, the dispatcher is set to SEQUENCE mode. I am guessing this is a threading issue with the Mock Response, is there any way to get around this? I am running SoapUI version 5.4.0. Many thanks Peter Mock Response - Script returned null Please could someone advise with the blow query. I have set up a Mock Response, which succesfully responds to the incomming request. I am trying to extract certain details from the inbound request using the 'SCRIPT' dispatch method. I have added the following line, but when I execute it returns 'Script returned [null]' def holder = new com.eviware.soapui.support.XmlHolder( mockRequest.requestContent ) Am I missed something as I can see the request arriving in the 'Request' window. Many thanks, Re: SoapUI - Cannot wait on null future Thanks but it doesn't appear to be down to memory. I have upgrade to SoapUI version 5.4.0 but still seeing the same issue. Could anybody please help? Thanks SoapUI - Cannot wait on null future Hi, When running a high thread count I am getting the following errors in SoapUI: java.lang.RuntimeException: cannot wait on null future It is very intermittent and only seems to happen with a high thread count (20+) I have built my test suite so that it is thread safe. There is one call out to a Test Case to increment an ID, which I call with the property “Run primary TestCase (with for running to finish)”. Other than that it is fairly simple script in calling a set of SOAP requests. I have switched off all assertions but still the issue persists. I am using SoapUI 5.0.0 (as this is the currently installed version on the corporate network). Many thanks.