Database bean Destroy

[Jason Webber <we...@mminternet.com>]

I have a database pooling bean that I use.  Is there a way to tell when the
bean is being destroyed becuase the bean has been replaced with a newer
version or is being unloaded for some reason?  I need to know so that I can
close the database connections that the bean is controlling.  I dont want to
wait for the connections just to timeout and have the database reclaim the
connection sessions.  This is because I sometimes get maximum sessions
exceeded with my oracle database.

TIA


--
To unsubscribe:   <ma...@jakarta.apache.org>
For additional commands: <ma...@jakarta.apache.org>
Troubles with the list: <ma...@jakarta.apache.org>

Getting multiple instances of my servlet, although it doesn't implement SingleThreadModel

[Scott Shorter <sh...@caradas.com>]

All,

I have a servlet that loads on startup, per the <load-on-startup/> tag
in web.xml.  It does *not* implement SingleThreadModel.

Unfortunately, two instances start up every time Tomcat starts - I can
tell because I have a System.out.println call in init().  I need for
there to be only one instance.

What other settings could be causing multiple instances to happen?

Thanks in advance,
Scott


--
To unsubscribe:   <ma...@jakarta.apache.org>
For additional commands: <ma...@jakarta.apache.org>
Troubles with the list: <ma...@jakarta.apache.org>