My application uses JTDS 1.3.1. It allows users to execute their own SP while we have no control on the SP being executed (i.e. can't edit them).
It's documented that by default JTDS will use client side cursor and cache the entire result set. In effect, we get out of memory exceptions.
We've tried appending useCursors=true to the connection string but that was ignored. We couldn't find a way to enforce server side cursors and apply a fetch size.
Is there an effective way to achieve that with JTDS working against Sybase 15.5?
BTW, when executing the same SP with Sybase isql there are no issues.
Thanks,
Shimoni
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
My application uses JTDS 1.3.1. It allows users to execute their own SP while we have no control on the SP being executed (i.e. can't edit them).
It's documented that by default JTDS will use client side cursor and cache the entire result set. In effect, we get out of memory exceptions.
We've tried appending useCursors=true to the connection string but that was ignored. We couldn't find a way to enforce server side cursors and apply a fetch size.
Is there an effective way to achieve that with JTDS working against Sybase 15.5?
BTW, when executing the same SP with Sybase isql there are no issues.
Thanks,
Shimoni