I dug a bit deeper here and I think that Camel is doing something with
the connection, possibly related to autoCommit.
I worked around the problem by writing my own Processor that sets
autoCommit to false, sets maxRows on the statement and then iterates
through the ResultSet and a cursor does seem to be used as expected.
But trying to do the same with the Camel JDBC component fails for
reasons described earlier.
Tim
On 06/11/2014 18:57, Claus Ibsen wrote:
So maybe its your maxRows=1000 that is the problem, so when you are
trying to get rows > 1000 then it throws that exception.
What is your use case? You want to select * from a table, but only the
first 1000 rows?
On Wed, Nov 5, 2014 at 10:05 PM, Tim Dudgeon <tdudgeon...@gmail.com> wrote:
On 05/11/2014 19:07, Claus Ibsen wrote:
maxRowSize ??? do you mean fetchSize?
Sorry, I mean maxRows (as in the example here:
http://camel.apache.org/jdbc.html).
So something like:
.to('jdbc:myDataSoruce?outputType=StreamList&statement.fetchSize=100&statement.maxRows=1000')
Also which version of Camel do you use?
2.14
Tim