Performance drop after 120 queries

I was testing my applet and decided to make it do over a hundred simple queries one after the other just to see how it would cope. Ive noticed that after 120 queries the speed of the applet reduces significantly.

What my program does is firstly connects to the MS Access database then for each new query it creates a query object and retrieves a ResultSet from the database.

Im not too sure as to what is the cause of the problem. I dont know if there is a limit on how many queries one connection to a database can handle or if I my method is consuming the memory available by creating many query objects. Also forcing the garbage collector to run on certain key presses to try and recover any lost memory doesnt seem to have any effect.

Any ideas?

Cheers

Andy

[805 byte] By [andycrolla] at [2007-9-26 1:16:17]
# 1
Do you call close() after you are done with ResultSets?A little note: you can not force garbage collection. System.gc() is only a suggestion to the gc. The gc will do its work fine without it if you only make sure that you don't keep referenses to no longer needed objects.
DanielN at 2007-6-29 0:43:56 > top of Java-index,Database Connectivity,Java Database Connectivity (JDBC)...
# 2
Is it the speed of the applet or the speed of the database that's tailing off?Is it the time for the query or the time for refreshing the display?
KPSeal at 2007-6-29 0:43:56 > top of Java-index,Database Connectivity,Java Database Connectivity (JDBC)...