Hi
TysonSouza,
To be clear....whatever query that is executed via the sql window (as well as when you execute the testcase containing the problematic JDBC step) always fails to execute no matter whether executing on a index, adding a where clause filter or attempting to restrict the returned resultset in some way so there isnt a default getfetchsize call made?
You also noticed when executing the test via querybuilder it executes fine, but when executing any other way it fails to retrieve thr resultset and this getfetchsize method issue is reported in the trace?
Sounds like you've done everything i would've tried to fix this yourself, but i don't think there's an easy way around this.
I dont actually know the querybuilder function other than clicking in it once or twice (second time being today) cos i just type in the sql in the sql form field.
Id suggest theres definitely a ReadyAPI! defect going on here as you can execute successfully via querybuilder but not from the sql window. The querybuilder populates the sql window with the dynamic generated sql, right? The thing is, the querybuilder is just building your query with an execution option to verify your query does what it wants, right?
Id raise a support ticket with smartbear for this....they need to know there is an issue interrogating CosmosDB emphasising there is no issue when executing via querybuilder, but there is a problem when executing the step and containing testcase.
The only thing i can suggest in the meantime (cos youve got a total blocker as far as i can see) whilst youre waiting for Smartbear to investigate is try upgrading and downgrading your driver .jar/JRE....perhaps a different version of .jar/JRE might get you around thr issue?
I know this sounds like a total longshot, but i had a "similar" problem with a totally different RDBMS called MIMER and altering the jre/.jar file versions got me around the problem.
Last longshot....can you downgrade your ReadyAPI! version...maybe v2.8 or v2.6? Maybe check the release notes and see if there were any changes to the jdbc component so worth downgrading to check?
Lastly i've been doing some reading....there's only been a CosmosDB connection driver for the last year....before then a driver wasnt available (raising the questions whats the point of a db you cant connect to!?!?!?) so perhaps there are teething troubles?
Oh...one last thing that sometimes catches people out....your ReadyAPI! has the same bittype (no i dont know the correct term) as your java, right? So if running x86 java you need 32bit ReadyAPI!, Likewise if youre running 64bit java then you need 64bit ReadyAPI!....this can cause problems if not lined up properly.
Ok..thats it from me...im sorry i cant be of more help....when raising the ticket with Smartbear ensure you mention youve already confirmed queyr executes successfully in dbvisualiser and works in querybuilder but not when executing the step
Cheers
Rich
