Many Statement/ResultSet using a single Connection

Question

Hi, all,
I'm a beginner to Java and JDBC, and i faced a problem doing some tests with JDBC.
My application is designed to be a 2 tier desktop application, with a single main frame where the user can open many child frames inside it. Each child frame could, for example, display a table in a grid, so i can have many grids showing many tables at the same time.
In my first test, i create a single connection, prepare 2 statements from this connection and get 2 result sets, one from each statement.
When i get the second result set, it throws an exception saying "The result set is closed".
I searched about his in Google, and found some articles saying it is not possible to have more than one opened resultset from one connection.
Is this information accurate?
If so, is there a way to workaround this? In my case, it would te too much expensive to open many connections for each user using the application, and it's not practical, at least now, to develod a third tier to the application, to share a connection pool, for example.
Maybe i'm not able to figure out some important aspect of working with JDBC, in this case i appreciate any advice that could help in my case.
Regards,
Fabiano

Answer 1

I presume if i decide to use a connection pool, i will need a separate application to act as itWrong.If your answer was supposed to get me curious, you got it :-)
So there is probably something wrong in my assumptions, so i would appreciate if you help to point where i am wrong.
My scenario is a local network with many computers (lets say 30) running my desktop (2-tier) application, all accessing the same database.
Today, in my actual application and in the above scenario, i will have 30 connections to the database, and the database server is starting to get busy to handle them all, so i don't want to raise the number of connections.
Reading your answer, i presume one of the following
a) your solution would be to use a connection pool inside each application instance
b) there is some better technique i'm not aware about and you do, because i'm used to write 2-tier applications and i'm blind to something simple and functional
In case of :
a) If each application's connection pool have an average of 5 connections, i will have 150 connection to the database, and it will probably starve.
b) I would appreciate if you point the name of the technique, framework, or some link so i can start to study and test it
Regards,
Fabiano