From: <forums_at_java.net>
Date: Mon, 10 Oct 2011 15:45:30 -0500 (CDT)

I have resolved it myself. Somehow in Glassfish when you open up a new
JDBC connection pool, it automatically adds a connection parameter
"useCursors" which is set to "True". Setting this to True ignores the
setMaxResults in our code, and brings the whole set of matching rows. Setting
it to False or deleting this property should put you back to expected result.

Hope this helps someone.

--
[Message sent by forum member 'rdarbh']
View Post: http://forums.java.net/node/851542