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 ...
Forum Discussion
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.
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.