ContributionsMost RecentMost LikesSolutionsRe: The JDBC driver [oracle.jdbc.driver.OracleDriver] is already registered. Found the issue. We have to reset our DB passwords every 60 days and I last had to update it at the same time as they made the server change to require a VPN connection to access the database. Oracle in their infinite wisdom allows you to create passwords that includes the at sign. SQLDeveloper apparently uses a connection string format which allows for this however the oracle jdbc driver connection strings do not because they use the at sign to denote the beginning of the server address (name or IP), then rather than giving a useful error code indicating that the connect string was incorrect they just throw an "unable to connect" error. Re: The JDBC driver [oracle.jdbc.driver.OracleDriver] is already registered. This seems to be the same issue but unfortunately no solution is offered https://stackoverflow.com/questions/9579142/connecting-to-oracle-using-vpn Re: The JDBC driver [oracle.jdbc.driver.OracleDriver] is already registered. That oracle issue is not the same as this and the solution will not work but I do think it tells me what the issue is. In the linked oracle issue they are setting an oracle database up on the local machine and then want to use it as a shared service. This causes an issue because it is requiring the network card to address itself. To solve the issue they add the loopback service which in effect creates a virtual network adapter and one is bound to the outbound call and the other to the response. In my case Oracle is not installed on the local machine, it is a remote server so the loopback service is irrelevant, however I do have 2 network interfaces, the physical card itself and a virtual one for the VPN connection which I have to be on to address the database server. If I had to guess SoapUi is for whatever reason continuing to use he physical network interface and not the VPN when making DB calls. Unfortunately even if this is the case it doesn't help because I don't see any way to force SoapUi to use the VPN connection Re: The JDBC driver [oracle.jdbc.driver.OracleDriver] is already registered. no we do not use a tnsnames.ora file Further even if we did that would not explain why I used to be able to connect to the database but cannot any longer as nothing about that has changed. Literally the only change was in network routing where I need to be on the VPN to access it however I verified that I can reach the database on the VPN by connecting via SQLdeveloper at the same time I was unable to connect via SoapUi The JDBC driver [oracle.jdbc.driver.OracleDriver] is already registered. Using SoapUI Pro in ReadyAPI 1.9.0 I am all of a sudden having trouble connecting to our Oracle Database. Testcases which have Database Steps in them which worked in the past can no longer connect. When I try to connect using the TestConnection button or run the query I get a pop up message that says java.sql.SQLException: Io exception: The Network Adapter could not establish the connection No error is thrown in the error log but in the ready!API Log the following message appears... The JDBC driver [oracle.jdbc.driver.OracleDriver] is already registered. The connection string is unchanged from when it previously worked and I have verified that I can access that database with Oracles SQLDeveloper using the same connection string. Other than upgrading from ReadyAPI 1.8.3 the only other thing that has changed is some network routing to the database, however given that I can connect to the database using SQL Developer that should not be the issue. I have also verified that the Oracle driver is in the readyAPI 1.9.0 ext folder. Finally the driver and my connect string format I am using are- oracle.jdbc.driver.OracleDriver jdbc:oracle:thin:{username}/{password}@{url}:{port}:{sid} Any idea what I can do to fix this or even start debugging why this is not working? SolvedRe: ERROR:java.io.IOException: Attempted read from closed stream Has anything been done with this because I am encountering the same thing using SoapUi 5.3.0... I have a rest request that returns 302 found and nothing else and SoapUi is throwing an IO and Null point error when I run that request Here is the SoapUi Log Tue Jul 11 12:56:32 EDT 2017:DEBUG:Attempt 1 to execute request Tue Jul 11 12:56:32 EDT 2017:DEBUG:Sending request: GET /messages/email/blacklist/bounce%40simulator.amazonses.com HTTP/1.1 Tue Jul 11 12:56:32 EDT 2017:DEBUG:Receiving response: HTTP/1.1 302 Found Tue Jul 11 12:56:32 EDT 2017:DEBUG:Connection can be kept alive indefinitely Tue Jul 11 12:56:32 EDT 2017:ERROR:An error occurred [Attempted read from closed stream.], see error log for details Tue Jul 11 12:56:32 EDT 2017:ERROR:Exception in request: java.lang.NullPointerException Tue Jul 11 12:56:32 EDT 2017:ERROR:An error occurred [java.lang.NullPointerException], see error log for details Tue Jul 11 12:56:32 EDT 2017:INFO:Error getting response for [Email-MS Api Documentation.blacklist:Request 1]; java.lang.NullPointerException Tue Jul 11 12:57:04 EDT 2017:DEBUG:Connection closed And the http log Tue Jul 11 12:56:32 EDT 2017:DEBUG:>> "GET /messages/email/blacklist/bounce%40simulator.amazonses.com HTTP/1.1[\r][\n]" Tue Jul 11 12:56:32 EDT 2017:DEBUG:>> "Accept-Encoding: gzip,deflate[\r][\n]" Tue Jul 11 12:56:32 EDT 2017:DEBUG:>> "Host: internal-email-ms-qa2-elb-1761796659.us-west-2.elb.amazonaws.com[\r][\n]" Tue Jul 11 12:56:32 EDT 2017:DEBUG:>> "Connection: Keep-Alive[\r][\n]" Tue Jul 11 12:56:32 EDT 2017:DEBUG:>> "User-Agent: Apache-HttpClient/4.1.1 (java 1.5)[\r][\n]" Tue Jul 11 12:56:32 EDT 2017:DEBUG:>> "[\r][\n]" Tue Jul 11 12:56:32 EDT 2017:DEBUG:<< "HTTP/1.1 302 Found[\r][\n]" Tue Jul 11 12:56:32 EDT 2017:DEBUG:<< "Access-Control-Allow-Headers: x-requested-with[\r][\n]" Tue Jul 11 12:56:32 EDT 2017:DEBUG:<< "Access-Control-Allow-Methods: POST,PUT,GET,OPTIONS, DELETE[\r][\n]" Tue Jul 11 12:56:32 EDT 2017:DEBUG:<< "Access-Control-Allow-Origin: *[\r][\n]" Tue Jul 11 12:56:32 EDT 2017:DEBUG:<< "Access-Control-Max-Age: 3600[\r][\n]" Tue Jul 11 12:56:32 EDT 2017:DEBUG:<< "Cache-Control: no-cache, no-store, max-age=0, must-revalidate[\r][\n]" Tue Jul 11 12:56:32 EDT 2017:DEBUG:<< "Date: Tue, 11 Jul 2017 16:56:32 GMT[\r][\n]" Tue Jul 11 12:56:32 EDT 2017:DEBUG:<< "Expires: 0[\r][\n]" Tue Jul 11 12:56:32 EDT 2017:DEBUG:<< "Pragma: no-cache[\r][\n]" Tue Jul 11 12:56:32 EDT 2017:DEBUG:<< "Server: Apache-Coyote/1.1[\r][\n]" Tue Jul 11 12:56:32 EDT 2017:DEBUG:<< "Strict-Transport-Security: max-age=31536000 ; includeSubDomains[\r][\n]" Tue Jul 11 12:56:32 EDT 2017:DEBUG:<< "X-Application-Context: application:qa,ijetDatasource:9443[\r][\n]" Tue Jul 11 12:56:32 EDT 2017:DEBUG:<< "X-Content-Type-Options: nosniff[\r][\n]" Tue Jul 11 12:56:32 EDT 2017:DEBUG:<< "X-Frame-Options: DENY[\r][\n]" Tue Jul 11 12:56:32 EDT 2017:DEBUG:<< "X-XSS-Protection: 1; mode=block[\r][\n]" Tue Jul 11 12:56:32 EDT 2017:DEBUG:<< "Content-Length: 0[\r][\n]" Tue Jul 11 12:56:32 EDT 2017:DEBUG:<< "Connection: keep-alive[\r][\n]" Tue Jul 11 12:56:32 EDT 2017:DEBUG:<< "[\r][\n]" and the Error Log Tue Jul 11 12:56:32 EDT 2017:ERROR:java.io.IOException: Attempted read from closed stream. java.io.IOException: Attempted read from closed stream. at org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:166) at org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:197) at org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:155) at org.apache.http.util.EntityUtils.toByteArray(EntityUtils.java:100) at org.apache.http.entity.BufferedHttpEntity.<init>(BufferedHttpEntity.java:60) at com.eviware.soapui.impl.wsdl.submit.transports.http.HttpMethodSupport.getResponseBody(HttpMethodSupport.java:237) at com.eviware.soapui.impl.wsdl.submit.transports.http.support.methods.ExtendedGetMethod.getResponseBody(ExtendedGetMethod.java:154) at com.eviware.soapui.impl.wsdl.submit.transports.http.SinglePartHttpResponse.<init>(SinglePartHttpResponse.java:51) at com.eviware.soapui.impl.wsdl.submit.filters.HttpPackagingResponseFilter.httpRequest(HttpPackagingResponseFilter.java:80) at com.eviware.soapui.impl.wsdl.submit.filters.HttpPackagingResponseFilter.afterAbstractHttpResponse(HttpPackagingResponseFilter.java:51) at com.eviware.soapui.impl.wsdl.submit.filters.AbstractRequestFilter.afterRequest(AbstractRequestFilter.java:64) at com.eviware.soapui.impl.wsdl.submit.transports.http.HttpClientRequestTransport.sendRequest(HttpClientRequestTransport.java:272) at com.eviware.soapui.impl.wsdl.WsdlSubmit.run(WsdlSubmit.java:119) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Tue Jul 11 12:56:32 EDT 2017:ERROR:java.lang.NullPointerException java.lang.NullPointerException at com.eviware.soapui.impl.wsdl.submit.transports.http.HttpClientRequestTransport.followRedirects(HttpClientRequestTransport.java:327) at com.eviware.soapui.impl.wsdl.submit.transports.http.HttpClientRequestTransport.sendRequest(HttpClientRequestTransport.java:242) at com.eviware.soapui.impl.wsdl.WsdlSubmit.run(WsdlSubmit.java:119) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Re: testcase.setPropertyValue is not updating the value between iterations of a loop using SoapUI 5.0.0, I just verified the same issue occurs in both ReadyAPI 1.4.1 and 1.5 Re: testcase.setPropertyValue is not updating the value between iterations of a loop using SoapUI 5.0.0, To give some background. This is a groovy script that controls a load test. You define a run duration (in either total seconds or an end time) and a number of test runs and the script will run through the number of defined test runs, then stop and restart the test. After the test duration has elapsed it executes some post processing scripts, in this particular case there is just 1 to be executed and all it does is query the results from out of the database and writes them to a spreadsheet but in other cases there could be other post processing (such as downloading log files from the tomcat servers and parsing them for information) . The reason why I have it break up the test runs into defined chunks is so that the results of a 4 hour test with more than 200,000 iterations of the test can be easier processed and represented into graphical format in excel (and the 64,000 row limit in excel is an issue too) . What this is trying to do is to iterate over the test runs and run the getStats script for each of them, the problem is it looks like the values of the properties of that testcase get loaded into the context and never updated even though the script is updating them. Re: testcase.setPropertyValue is not updating the value between iterations of a loop using SoapUI 5.0.0, A testcase... def postProc = testRunner.testCase.testSuite.project.testSuites[suiteName].testCases["postProcessingScripts"] testcase.setPropertyValue is not updating the value between iterations of a loop using SoapUI 5.0.0, In the following code... def getStats = postProc.testSteps["getStatsForRun"] runList.each{ sleep (4000) log.info "getting stats for run: runName = ${it.runName}, runId = ${it.runId}" postProc.setPropertyValue("runName", it.runName) postProc.setPropertyValue("runId", it.runId) log.info "runName = ${postProc.getPropertyValue("runName")} , runId = ${postProc.getPropertyValue("runId")}" sleep (4000) getStats = postProc.testSteps["getStatsForRun"] getStats.run(testRunner, context) } The values of the properties runName and runId are only being updated on the first iteration of the loop. I can see in the logging that the list is being properly iterated but every time the getStatsForRun step is executed it uses the values of the first element in the list. Is this a known issue in 5.0.0? If so is it resolved in the latest version of readyAPI?