I tracked it down a bit. Its something to do with auto commit.
There's something about it here:
http://www.postgresql.org/message-id/083dbfcc-8eac-4a5f-bd61-3a82dfc45...@visualdistortion.org
In my case I tried using the resetAutoCommit=false property on the JDBC
component, and thought it had worked, but it seems that what happened is
that it now runs with autoCommit=true which means the maxRows property
is ignored and the whole ResultSet gets loaded and I then get OOM
errors. So back to square 1 :-(
Seems like Camel is doing something with autoCommit which Postgresql is
not liking.
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
