Forum Discussion

ocmyhome's avatar
ocmyhome
New Contributor
12 years ago

4.6.4 freezes when executing a jdbc request

When executing this jdbc request test step, it freezes every time using 4.6.4. When using 4.6.3, I get no freeze whatsoever. I copied over the jdbc driver to it's proper location in the new install as well.

I'm executing a simple select request:
select * from Table
where ColumnName = '${#Project#CustServer}'

This isn't critical for me as I'll merely uninstall 4.6.4 and use 4.6.3 but wanted to inform SmartBear. Please reply with any additional questions that can help get this resolved...

Below is the log error:

2014-03-07 12:06:28,026 ERROR [errorlog] com.eviware.soapui.support.SoapUIException: Failed to init connection for drvr [com.microsoft.sqlserver.jdbc.SQLServerDriver], connectionString [jdbc:sqlserver://ServerName;databaseName=DBName;user=sa;password=SAPassword;]
com.eviware.soapui.support.SoapUIException: Failed to init connection for drvr [com.microsoft.sqlserver.jdbc.SQLServerDriver], connectionString [jdbc:sqlserver://ServerName;databaseName=DBName;user=sa;password=SAPassword;]
at com.eviware.soapui.support.jdbc.JdbcUtils.initConnection(JdbcUtils.java:64)
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 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)

6 Replies

  • Hello,

    What JDBC driver you are using? What particular version you are using?
    The stack trace shows you are not able to successfully connect. Does it freeze only on connection failure or other times?
    Are there any crash logs generated in the SoapUI install directory?

    If I know the exact JDBC driver you are using I could try to replicate the issue locally.


    Thanks.
  • ocmyhome's avatar
    ocmyhome
    New Contributor
    Thanks for replying. See below in red...

    What JDBC driver you are using? I use version "sqljdbc.jar". From some investigation there's a "sqljdbc4.jar" version out there apparently as well. I use the prior.
    What particular version you are using? For the JDBC driver I couldn't find any additional details other than these two versions (me using "sqljdbc.jar"). Let me know if you meant something else.
    The stack trace shows you are not able to successfully connect. Does it freeze only on connection failure or other times? It freezes whenever I attempt to execute that test step, every time. I'm not sure what other variations I'd test other than the sql syntax itself (select Vs update, etc).
    Are there any crash logs generated in the SoapUI install directory? Nope, no logs.

    If I know the exact JDBC driver you are using I could try to replicate the issue locally.

    Additional information: I use a reference (eg: ${#Project#JdbcDriver}) for the jdbc driver and connection string. I'm running against SQL 2012.
  • We have the same problem with JDBC requests in 4.6.4 version. Tests randomly hangs at ModelItemIconAnimator run loop:

    java.lang.Thread.State: TIMED_WAITING (sleeping)
    at java.lang.Thread.sleep(Native Method)
    at com.eviware.soapui.impl.wsdl.support.ModelItemIconAnimator.start(ModelItemIconAnimator.java:86)
    at com.eviware.soapui.impl.wsdl.panels.teststeps.JdbcRequest$RequestIconAnimator.beforeSubmit(JdbcRequest.java:343)
    at com.eviware.soapui.impl.wsdl.panels.teststeps.JdbcSubmit.run(JdbcSubmit.java:152)
    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:235)
    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 com.eviware.soapui.impl.wsdl.support.AbstractTestRunner.start(AbstractTestRunner.java:77)
    at com.eviware.soapui.impl.wsdl.testcase.WsdlTestCase.run(WsdlTestCase.java:640)
    at pl.autoguard.it.ac2server.altar.AltarSoapUIRunner.runTestCase(AltarSoapUIRunner.java:85)
    at pl.autoguard.it.ac2server.altar.AltarSoapUIITCase.runTestCase(AltarSoapUIITCase.java:132)
    at pl.autoguard.it.ac2server.altar.AltarSoapUIITCase.altarSoapUIAddMinimalDevice(AltarSoapUIITCase.java:49)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:606)



    We'are using postgresql-9.1-901.jdbc4 driver.
  • - Had the same error on a groovy loop with HTTP requests and the same sleeping thread:
    java.lang.Thread.State: TIMED_WAITING (sleeping)
    at java.lang.Thread.sleep(Native Method)
    at com.eviware.soapui.impl.wsdl.support.ModelItemIconAnimator.start(ModelItemIconAnimator.java:86)
    (...)
    - Got the patch from "#632 Concurrency bug in ModelItemIconAnimator.java " http://sourceforge.net/p/soapui/bugs/632/
    - javac + jar u for updating soapui-4.6.4.jar file with the new class.
    - Now it works.

    A look at https://github.com/SmartBear/soapui/com ... mator.java shows this patch has never been applied to the trunk.
  • Hi,

    I will notify development of this. The fix appears to be done by someone who never made a pull request to check the fix in.
  • We have made some improvements to the icon animator in 5.0.0, similar to the fix linked here, but not exactly the same solution. Could you have a try with 5.0.0 and see if the problem still occurs?

    Regards
    Joel Jonsson
    SmartBear Sweden