Re: OutOfMemory and IOException Access Denied errors

2006-05-22 Thread Dan Armbrust
Your out of memory error is likely due to a mysql bug outlined here: http://bugs.mysql.com/bug.php?id=7698 Thanks for the article. My query executed in no time without any errors !!! The MySQL drivers are horrible at dealing with large result sets - that article gives you the workaround to

Re: OutOfMemory and IOException Access Denied errors

2006-05-19 Thread Rahil
Hi Dennis Dennis Watson wrote: Hi Rahil, Your out of memory error is likely due to a mysql bug outlined here: http://bugs.mysql.com/bug.php?id=7698 There is a work around presented in the article. I have been able to select large datasets from mysql while indexing by using the SQL_BIG_RE

Re: OutOfMemory and IOException Access Denied errors

2006-05-19 Thread Dennis Watson
Hi Rahil, Your out of memory error is likely due to a mysql bug outlined here: http://bugs.mysql.com/bug.php?id=7698 There is a work around presented in the article. I have been able to select large datasets from mysql while indexing by using the SQL_BIG_RESULT hint in mysql and pumping up

Re: OutOfMemory and IOException Access Denied errors

2006-05-19 Thread Rahil
Thanks Paul and Otis I basically applied the same mechanism used in creating indexes in MySQL to Lucene. So I didnt use any fetchSize. But Ill implement it now and see how it performs. Will also look into DBSight. However when executing the query by limiting the result set to 10 the quer

Re: OutOfMemory and IOException Access Denied errors

2006-05-19 Thread Paul . Illingworth
I guess you are executing your SQL and getting the whole result set. There are options on the JDBC Statement class that can be used for controlling the fetch size - by using these you should be able to limit the amount of data returned from the database so you don't get OOM. I haven't used the

Re: OutOfMemory and IOException Access Denied errors

2006-05-19 Thread Otis Gospodnetic
It's impossible to tell from the code you provided, but you are most likely just leaking memory/resources somewhere. For example, ResultSet's and other DB operations should typically be placed in a try/catch/FINALLY block, where the finally block ensures all DB resources are closed/released. O