Hi: When I use JPA with Hibernet, when dealing with large table, looks like maxMessagesPerPoll is not functioning as designed, as the memory grows indicating Camel JPA is indeed retrieving the entire table instead of the indicated poll size?
The entity being comsumed has a one-to-many relationship to another entity. Also, when I use maximumResults option instead, seems that Camel JPA hangs, but without memory grow. Might be an indication that the real query to database is now very slow. I think I might not be using the JPA correctly, could some one here point out the right way? -- View this message in context: http://camel.465427.n5.nabble.com/Camel-JPA-s-maxMessagesPerPoll-and-maximumResults-problem-tp4007628p4007628.html Sent from the Camel - Users mailing list archive at Nabble.com.
