In the future, please don't reply to other's post w/ a different topic. "Gareth Coltman" <[EMAIL PROTECTED]> writes:
> We are having problems with database connections disconnecting unexpectedly after 1 >hour, whether or not that have been used during > this period. After exploring our network and database configurations, it seems the >only culprit can be Turbine (we are using 2.1). I > have tried to track down the code in Turbine which causes the connections to expire >but can't. I have found the isExpired method in > the ConnectionPool class : > > return ((System.currentTimeMillis() - > connection.getTimestamp()) > expiryTime); > > - this is interesting because it expires whether or not it has been active during >that period. However I can't find any thread that > monitors the connections and expires them. Obviously missing something. Ideally what >one would want is for connections to remain > cached up to expiry_time after they were last used. Anyway, please help! What database are you using? Are you using Torque to handle the database connections? Are you ever using a DBConnection object directly, and if so are you remembering to return the connection to the pool using a try/finally block? -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
