Forum Discussion

charsnonumber's avatar
charsnonumber
New Contributor
11 years ago

[Res] DB Connection string is not updated when changing env

Hi,

I'm running 4.5.2 (PRO) on Windows 7 PC.

There is a problem when switchning between environments. The DataBase (DB2) connections are not changed.
The user must run each test step that contains database request first once as a test step to make the right connection.
This problem was actually solved in "soapUI Pro 4.5.1-NB-SNAPSHOT", but has come back.

In my case I have the DataBase access in a test case that the main test case access by use of "Run TestCase" test step,
but I don't think this makes any differense.

If I use the 4.5.1-NB-SNAPSHOT this work fine when using the GUI.
But, I also need to run, using schtasks, testrunner.bat. That is to run tests at certain times during night.
In this case, not even 4.5.1-NB-SNAPSHOT woks ok. There the fix doesn't work, problem remains. I use the -E switch to select environment.

Hope you can help me with this!

Best Regards
Anders D.
Sweden

Ps. when I run 4.5.1-NB-SNAPSHOT and got the offer to upgraede to 4.5.2, there was a popup that was a pop-up that should describe the changes, but it just said something like: no information available. Ds.
Pps. I have a PRO, registered in a group, whith owner: Anna Reimer, Bankgirocentralen BGC AB. Dds.

17 Replies

Sort By
  • SiKing's avatar
    SiKing
    Community Expert
    11 years ago
    This is a known issue. I personally submitted this as a defect, SmartBear acknowledged it, it's a low priority. If you have the -Pro license, contact them to vote it up.

    The workaround that I use is to place the db server into a Project property, and then modify my connect string to look something like:
    jdbc:mysql://${#Project#dbServer}:3306/schema
    You can then modify the variable dbServer for each of your environments.

    HTH
  • charsnonumber's avatar
    charsnonumber
    New Contributor
    11 years ago
    Hi,
    Thanks for the suggestion, I will try that, It's probably a good working solution.
    I also believe I can solve it by making the accesss (in some way) from groovy.

    As I'm here at a consultant basis and the licenses are bought as a bunch, it is not obvious how to register as a PRO user. But I will.

    As you probably also know the defect was partly solved in the previous snapshot release, so I can't see why it wasn't included in the 4.5.2 release.

    Best Regards
    A.
  • SiKing's avatar
    SiKing
    Community Expert
    11 years ago
    charsnonumber wrote:
    As you probably also know the defect was partly solved in the previous snapshot release, so I can't see why it wasn't included in the 4.5.2 release.

    What? Where? I did not see anything.
  • SagarArcher's avatar
    SagarArcher
    New Contributor
    11 years ago
    Hi Everyone,

    Has there beeen any update on this? I continue to face the same issue in the latest SOAP UI Pro version - 4.6.0.
    This seems to be working on the SOAP UI Pro 4.5.2m SNAPSHOT version though.

    Regards,
    Sagar
  • MarcusJ's avatar
    MarcusJ
    Moderator
    11 years ago
    This is a known issue. I personally submitted this as a defect, SmartBear acknowledged it, it's a low priority. If you have the -Pro license, contact them to vote it up.


    Siking,

    Did you receive the defect number for this?

    SagarArcher the latest version is SoapUI 4.6.1, are you able to reproduce this problem using latest version?
  • SiKing's avatar
    SiKing
    Community Expert
    11 years ago
    mrJames wrote:
    Did you receive the defect number for this?

    The SmartBear support is not very good at sending back jira numbers ... and I heard you guys upgraded your jira to boot. I only have an email tracking number, and I do not know how useful that is: HKY-823-33367
  • MarcusJ's avatar
    MarcusJ
    Moderator
    11 years ago
    Thanks for the ticket number.

    Defect number SOAP-15 is being used to track this.
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    SmartBear Alumni (Retired)
    11 years ago
    Just checked and this functionality works just fine in SoapUI Pro v4.6.1. Just make sure you have the configuration set correctly:

    1. In Project > JDBC Connection tab; define a JDBC connection. e.g. let's call it "SUI_JDBC_Conn"
    2. Now in Project > Environments tab, click on each environment and 'JDBC Connection' subtab. Change the connection details there.

    After the above config, changing environments changed the credentials in my case. Please confirm if that doesn't work for you. And if so, can you please attach the screenshots:
    - Project > JDBC Connection tab
    - Project > Environments tab > 'JDBC Connection' subtab; per environment

    Thanks,
    Michael Giller
    SmartBear Software
    • nuv7's avatar
      nuv7
      Occasional Contributor
      5 years ago

      Hello,

       

      I am using Ready API 2.8 and I am having the same problem.  Anyone know how to solve this problem?

       

      Thank you for your help.

      • sonya_m's avatar
        sonya_m
        SmartBear Alumni (Retired)
        5 years ago

        Hi nuv7,  have you tried using workarounds suggested in this thread?  

         

        I’ve also checked our DB and see that this issue was fixed in version 2.6, so it is supposed to work fine.

        Your case definitely requires deeper investigation, please contact support and provide them with the details of your issue, thank you.  

  • SiKing's avatar
    SiKing
    Community Expert
    11 years ago
    I take that back: there is still a problem! I am not sure exactly where the problem is though.


    1. create a project

    2. create a JDBC connection

    3. create an Environment

    4. create a test that used the JDBC connection

    5. verify everything is working, save everything, exist SoapUI (just in case)

    6. create another Environment

    7. run the testcase against this new environment

    8. the JDBC step never gets executed, the testcase stops at that point with the below errors

    9. the workaround that I have found: you need to open and close every single JDBC step 



      10. 2013-11-01 13:10:46,913 INFO  [SoapUIProTestCaseRunner] Running soapUI testcase [createClientKey TestCase]
      2013-11-01 13:10:46,913 INFO  [SoapUIProTestCaseRunner] running step [check validateHash]
      2013-11-01 13:10:47,283 INFO  [SoapUIProTestCaseRunner] Assertion [Not SOAP Fault] has status VALID
      2013-11-01 13:10:47,283 INFO  [SoapUIProTestCaseRunner] Assertion [EXISTS validateHash] has status VALID
      2013-11-01 13:10:47,283 INFO  [SoapUIProTestCaseRunner] running step [retrieve appSignatureHash]
      2013-11-01 13:10:49,723 ERROR [SoapUI] An error occured [Communications link failure

      The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.], see error log for details
      2013-11-01 13:10:49,723 ERROR [errorlog] com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure

      The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.
      com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure

      The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.
       at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
       at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
       at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
       at java.lang.reflect.Constructor.newInstance(Unknown Source)
       at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
       at com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1117)
       at com.mysql.jdbc.MysqlIO.<init>(MysqlIO.java:350)
       at com.mysql.jdbc.ConnectionImpl.coreConnect(ConnectionImpl.java:2408)
       at com.mysql.jdbc.ConnectionImpl.connectOneTryOnly(ConnectionImpl.java:2445)
       at com.mysql.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:2230)
       at com.mysql.jdbc.ConnectionImpl.<init>(ConnectionImpl.java:813)
       at com.mysql.jdbc.JDBC4Connection.<init>(JDBC4Connection.java:47)
       at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
       at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
       at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
       at java.lang.reflect.Constructor.newInstance(Unknown Source)
       at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
       at com.mysql.jdbc.ConnectionImpl.getInstance(ConnectionImpl.java:399)
       at com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:334)
       at com.eviware.soapui.support.GroovyUtils$DriverProxy.connect(GroovyUtils.java:171)
       at java.sql.DriverManager.getConnection(Unknown Source)
       at java.sql.DriverManager.getConnection(Unknown Source)
       at com.eviware.soapui.support.jdbc.JdbcUtils.initConnection(JdbcUtils.java:68)
       at com.eviware.soapui.impl.wsdl.panels.teststeps.JdbcSubmit.getDatabaseConnection(JdbcSubmit.java:218)
       at com.eviware.soapui.impl.wsdl.panels.teststeps.JdbcSubmit.prepare(JdbcSubmit.java:261)
       at com.eviware.soapui.impl.wsdl.panels.teststeps.JdbcSubmit.runQuery(JdbcSubmit.java:197)
       at com.eviware.soapui.impl.wsdl.panels.teststeps.JdbcSubmit.run(JdbcSubmit.java:161)
       at com.eviware.soapui.impl.wsdl.panels.teststeps.JdbcSubmit.<init>(JdbcSubmit.java:75)
       at com.eviware.soapui.impl.wsdl.panels.teststeps.JdbcRequest.submit(JdbcRequest.java:135)
       at com.eviware.soapui.impl.wsdl.teststeps.JdbcRequestTestStep.run(JdbcRequestTestStep.java:205)
       at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.runTestStep(AbstractTestCaseRunner.java:239)
       at com.eviware.soapui.impl.wsdl.testcase.WsdlTestCaseRunner.runCurrentTestStep(WsdlTestCaseRunner.java:48)
       at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.internalRun(AbstractTestCaseRunner.java:148)
       at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.internalRun(AbstractTestCaseRunner.java:43)
       at com.eviware.soapui.impl.wsdl.support.AbstractTestRunner.run(AbstractTestRunner.java:135)
       at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
       at java.util.concurrent.FutureTask$Sync.innerRun(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)
      Caused by: java.net.UnknownHostException: unused
       at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method)
       at java.net.InetAddress$1.lookupAllHostAddr(Unknown Source)
       at java.net.InetAddress.getAddressesFromNameService(Unknown Source)
       at java.net.InetAddress.getAllByName0(Unknown Source)
       at java.net.InetAddress.getAllByName(Unknown Source)
       at java.net.InetAddress.getAllByName(Unknown Source)
       at com.mysql.jdbc.StandardSocketFactory.connect(StandardSocketFactory.java:249)
       at com.mysql.jdbc.MysqlIO.<init>(MysqlIO.java:300)
       ... 34 more
      2013-11-01 13:10:49,793 INFO  [SoapUIProTestCaseRunner] Assertion [JDBC Status] has status UNKNOWN
      2013-11-01 13:10:49,793 INFO  [SoapUIProTestCaseRunner] Assertion [VERIFY md5] has status UNKNOWN
      2013-11-01 13:10:49,793 ERROR [SoapUIProTestCaseRunner] retrieve appSignatureHash failed, exporting to [C:\Users\XXX\workspace\das-war-test\soapui\results\DeviceAuth_Smoke_TestSuite-createClientKey_TestCase-retrieve_appSignatureHash-0-FAILED.txt]
      2013-11-01 13:10:49,803 ERROR [SoapUIProTestCaseRunner] Error saving failed result: java.lang.NullPointerException
      java.lang.NullPointerException
       at java.io.StringReader.<init>(Unknown Source)
       at org.apache.xmlbeans.impl.store.Locale.parse(Locale.java:708)
       at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:696)
       at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:683)
       at org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:208)
       at org.apache.xmlbeans.XmlObject$Factory.parse(XmlObject.java:580)
       at com.eviware.soapui.support.xml.XmlUtils.createXmlObject(XmlUtils.java:263)
       at com.eviware.soapui.support.XmlHolder.<init>(XmlHolder.java:38)
       at com.eviware.soapui.impl.wsdl.teststeps.JdbcTestStepResult.writeTo(JdbcTestStepResult.java:224)
       at com.eviware.soapui.tools.SoapUITestCaseRunner.afterStep(SoapUITestCaseRunner.java:722)
       at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.runTestStep(AbstractTestCaseRunner.java:251)
       at com.eviware.soapui.impl.wsdl.testcase.WsdlTestCaseRunner.runCurrentTestStep(WsdlTestCaseRunner.java:48)
       at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.internalRun(AbstractTestCaseRunner.java:148)
       at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.internalRun(AbstractTestCaseRunner.java:43)
       at com.eviware.soapui.impl.wsdl.support.AbstractTestRunner.run(AbstractTestRunner.java:135)
       at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
       at java.util.concurrent.FutureTask$Sync.innerRun(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)
      2013-11-01 13:10:49,823 INFO  [SoapUIProTestCaseRunner] Finished running soapUI testcase [createClientKey TestCase], time taken: 2870ms, status: FAILED


      I have a new environment, but no workaround for this.