That said, I would expect JCC driver also to work with 10.1 Derby
server. Do you have any errors in your derby.log? I would also set
Derby properties 'derby.language.logStatementText=TRUE' and 'derby.stream.error.logSeverityLevel=0'
and run the test again. This would provide more useful info to diagnose
the problem.

Satheesh

Aaron Rothschild wrote:

Hello Mailing List,
we use a type_scroll_insensitive resultset to allow for moving back one
record using a call to [resultSet].previous(). That works fine as long as we
use our database in embedded mode. Once we switch to the network mode with
the db2jcc.jar driver, a heap overflow results. We assume that this is the
result of continuous attempts of the network driver to retrieve resultsets.
Has this been witnessed before? Are there feasible solutions?
(We currently try to *circumvent* the problem by building a new sql query
that makes calls to "previous()" superfluous.)
Regards,
Aaron.
____________
Virus checked by G DATA AntiVirusKit
Version: AVK 16.1430 from 05.11.2005
Virus news: www.antiviruslab.com