A JDBC Realm is just a tool to authenticate and authorize an user against a database. So it has nothing to do with your problem.
As said earlier finalize() won't help you, as the time when a servlet instance is destroyed is undetermined. It might never be destroyed until tomcat is shut down. How you can achieve your goal is not easy to say, as it requires more knowledge about your application. It's quite unclear to me when and under which circumstances you want to close the connections. The socke write error you reported indicates, that you keep the connection open to long. > -----Ursprüngliche Nachricht----- > Von: Christian J. Dechery [mailto:[EMAIL PROTECTED]] > Gesendet: Dienstag, 11. Juni 2002 18:30 > An: [EMAIL PROTECTED] > Betreff: Re: AW: problem with connections not closing... > > I was thinking of some type os static variable to control it > on the super DAO class. There is a super DAO class which all > the DAO inherit the connection object from, I wrote the > finalize() and cleanUp() code in there... I was thinking of a > solution that would use this class. > > But what about the JDBC Realm? I still don't know what it is, > and what it's for. > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
