Folks,

First let me thank for all those replied to this thread. But looks like only two have got the idea, of what I'm talking about. When you are using the middle tire application, then I would think that it would be a good choice to hadle things on the middle tier rather than on the database tier, unless and otherwise you are restricted with the resources. The two of those who are close to my question were Shestakov and nagarjuna.

Now let me further debrief my question. As you folks put, the weblogic is using connection pooling. I'm least bothered about the number of inactive sessions. What I'm bothered was the number of active sessions. What puzzles me was that the number of active sessions doesn't seems to go beyond a certain number, even when the application is getting pounded. In my case it was 20. So, I'm wondering whether there are any parameter settings on the weblogic server that controlls the number of concurrent sessions/connections that can be handled against the database?

Once again thanks,

Sam