There's either a memory leak or a connection leak in the ODBC bridge. I'm not sure which. I have a site using sql server w/jrun and prior to switching to a new interface (other than the odbc-jdbc bridge) I was seeing my handles increasing (and connections) but never subsiding. Eventually after a day to a week I'd have to reboot to free up the resources. And the machine would hang sometimes if I didn't get to it first. What it depended on was how many people had been booked in the system (it's a log for a jail). After changing drivers to a pure jdbc sql server interface I haven't had to reboot in a couple of monthes, and I don't have the resource problems that I was having.
--mikej -=----- mike jackson [EMAIL PROTECTED] > -----Original Message----- > From: Josh G [mailto:[EMAIL PROTECTED]] > Sent: Thursday, August 29, 2002 4:16 PM > To: Tomcat Users List > Subject: Re: Database write delay?!?!?!? > > > On Fri, 30 Aug 2002 8:47 am, Mike Jackson wrote: > > > Are you using the JDBC-ODBC bridge? If so then I'd not worry about > > the delayed writes, I'd worry about restarting your app often > > (daily/weekly), and your database engine for that matter. > > > > Feel like explaining that one? Is there a bug in the bridge? Or > are you just > giving me the tired old "it's on windows so reboot it twice a day" speech? > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
