JDBC connection and storing in session till it expires?

I have implemented logging mechanism in Oracle by the way of a stored procedure. And in java, I am having a class which has different methods that is called from different places of my application. It has constructor which creates sql connection. The methods make calls to the stored procedure with appropriate parameters. But once the user comes to the site, I want the jdbc connection to be made to oracle and use the same connection throughout the user session. This is accomplished by putting the connection object into the session. Then by retrieving the connection object from session before any method call is made, I make the object's method call. And I want to close the connection finally when the user session ends.

To make it clear, plz see the sample code format,

import java.sql.CallableStatement;
import java.sql.Connection;
import java.sql.DriverManager;
 
 public class DbTest { 
   private static String url = "jdbc:oracle:thin:@localhost:7001:xe";
   private static String username = "";
   private static String password = ""; 
   private Connection conn = null; 
 
 public DbTest() {  
    Class.forName("oracle.jdbc.driver.OracleDriver");
     conn = DriverManager.getConnection(url, username, password);
     }   

public void log1(String param1, String param2...) { 
 try {
  CallableStatement stmt = conn.prepareCall("{call SP (?, ?)}");
   stmt.setString(1, param1);
  stmt.setString(2, param2);
  stmt.execute(); 
  } 
catch (SQLException e) { 
  e.printStackTrace(); 
  }  
}  

public void log2(String param1, String param2...) {
 ... 
... 
}  
} //End of DbTest class


   import DbTest;
  public class userEnteringClass {

  public void caller() {
  DbTest dbtest = (DbTest)session.getAttribute("DbTest");
 if (dbtest == null)
 { 
dbtest = new dbtest();
 session.setAttribute("DbTest", dbtest);
 }
  .... 
 dbtest.log1(param1, param2);
 ....
 ....
 dbtest.log2(param1, param2);
 ...
 } 
}

Open in new window


Hope you got what I am trying to do.
If this is not a good way, then plz suggest a better way. If possible with a sample code. Thanks for any help
weblogicmeAsked:
Who is Participating?
 
petiexCommented:
The short answer is, don't do that. Use connection pooling. Whenever a database transaction is required, get a connection from the connection pool, do the transaction in a try block that catches SQL or other exceptions, and close the connection in a finally block to return it to the pool. Whatever you are using as an application- or web- server, google that with "connection pool", and you will likely get a good lead on how to do this.

Under your current scenario, if you have more concurrent sessions than available db connections, you run out of connections. It seems that a single user can exhaust your database by logging in and closing his browser repeatedly, because there's really no way of knowing when somebody ends a session (e.g., by closing the browser) before the session expires. Multiple abandoned sessions = multiple open connections = overburdened db server and angry DBAs.
0
 
for_yanCommented:
perhpas this would help which shows how to call method befioere session expires:

http://stackoverflow.com/questions/3943368/invoke-method-just-before-session-expires
0
 
for_yanCommented:
I think thsi is on the similar subject, check the accepted solution:

http://stackoverflow.com/questions/7756054/how-to-call-a-method-before-the-session-object-is-destroyed
0
Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

 
for_yanCommented:
also read comments below the solution (same that I posted above):

http://stackoverflow.com/questions/7756054/how-to-call-a-method-before-the-session-object-is-destroyed

the comments  seem to be useful
0
 
Sathish David Kumar NArchitectCommented:
User Iterceptor concept ... in that you can check pre- request and post-request also
0
 
weblogicmeAuthor Commented:
So I can implement connection pooling as mentioned here?
http://java.sun.com/developer/onlineTraining/Programming/JDCBook/conpool.html

It mentiones "The wrapper approach works particularly well in an Enterprise Bean that uses Bean-managed persistence for two reasons: 1) Only one Driver class is loaded per Bean, and 2) specific connection details are handled outside the Bean. "

For my DBLog approach , is it ok to put it in wrapper class? Because I am not creating any entity bean...
0
 
petiexCommented:
I've honestly never had to worry about the implementation of a Connection Pool, because the app servers I have used, Websphere and Glassfish, both have a built in connection pool facility which you configure to point to your data sources using their respective web-based admin consoles. You just need to provide it the login credentials, db name and server address, port number, any proprietary db access jar files, and a jndi name to look it up by. Then in your application, you access the data source using a JNDI lookup.

You might look into whether the app server or web server you are using has such a facility built-in. The odds are pretty good that it does.

If you only have one data source, it might actually be simpler to roll your own Connection Pool as described in that tutorial you linked to. As far as I can tell, there is no requirement to be using entity beans; they just point out that it's particularly well suited for them.
0
 
weblogicmeAuthor Commented:
Thanks
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.