JDBC connection and storing in session till it expires?

Posted on 2012-03-16
Last Modified: 2012-08-13
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() {  
     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);
catch (SQLException e) { 

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
Question by:weblogicme
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
  • 2
  • +1
LVL 47

Expert Comment

ID: 37728162
perhpas this would help which shows how to call method befioere session expires:
LVL 47

Expert Comment

ID: 37728191
I think thsi is on the similar subject, check the accepted solution:
LVL 47

Expert Comment

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

the comments  seem to be useful
PeopleSoft Has Never Been Easier

PeopleSoft Adoption Made Smooth & Simple!

On-The-Job Training Is made Intuitive & Easy With WalkMe's On-Screen Guidance Tool.  Claim Your Free WalkMe Account Now

LVL 20

Expert Comment

by:Sathish David Kumar N
ID: 37728371
User Iterceptor concept ... in that you can check pre- request and post-request also
LVL 11

Accepted Solution

petiex earned 500 total points
ID: 37730882
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.

Author Comment

ID: 37733123
So I can implement connection pooling as mentioned here?

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...
LVL 11

Expert Comment

ID: 37739237
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.

Author Closing Comment

ID: 37797779

Featured Post

Get 15 Days FREE Full-Featured Trial

Benefit from a mission critical IT monitoring with Monitis Premium or get it FREE for your entry level monitoring needs.
-Over 200,000 users
-More than 300,000 websites monitored
-Used in 197 countries
-Recommended by 98% of users

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

By the end of 1980s, object oriented programming using languages like C++, Simula69 and ObjectPascal gained momentum. It looked like programmers finally found the perfect language. C++ successfully combined the object oriented principles of Simula w…
Java had always been an easily readable and understandable language.  Some relatively recent changes in the language seem to be changing this pretty fast, and anyone that had not seen any Java code for the last 5 years will possibly have issues unde…
This tutorial covers a practical example of lazy loading technique and early loading technique in a Singleton Design Pattern.
This tutorial will introduce the viewer to VisualVM for the Java platform application. This video explains an example program and covers the Overview, Monitor, and Heap Dump tabs.
Suggested Courses

628 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question