• Post Reply Bookmark Topic Watch Topic
  • New Topic

JDBC pool monitor, bean monitor and others  RSS feed

Howard Zhao
Posts: 27
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
In my applet � http  servelt �JDBC  DB model, when the applet sends a request to servelt, the servlet picks up a JDBC connection from connection pool and assigns the connection dedicated to serve the applet. Since the applet sends many request (one after another, not simotaneously) to servlet during applet life time, the servlet needs to know, in order to serve the specfic applet, it needs to find the dedicated JDBC connection to offer service to the applet.
Because when JDBC connection finishes serving a request sent by applet, the connection can not be put into the connection pool, instead, it is put into a servlet hashtable table so that at next request, which is sent by same applet, the servlet can pick up the connection from the hashtable in order tokeep the dedicated service to the applet.
My question is since weblogic has a console to monitor the behaviour of connection pool and connections,
I do not know whether my above try has some impact on the monitoring or on some other weblogic features. Can someone tell me?
Another question is since I use a stateful session bean as a timer to time out a connection when the onnection is out of the pool (in other words, for each JDBC connection, when it is out of the pool, a stateful session bean is created to be a timer to time out the connection), and the bean dose nothing but timing. When times up, it gets itself removed and on the same time, the JDBC connection the bean is timing on will be closed and put back to the JDBC connection pool.
My question is can I use a stateful session bean like this? Whether there will be some impacts on the console bean monitoring , JDBC monitoring or other things?
Thanks in advance.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!