It is a good idea to expire a connection after several hours or possibly a day or two, regardless of whether the connection is being used during that time. I do not know the reason for this, but connections tend to get stale. If you set the expiration to only occur after the connection has not been used for the given amount of time, it likely will never expire until it goes bad.
john mcnally Gareth Coltman wrote: > > 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! > > Gareth > > -- > 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]>
