We are sure there is a timeout, because we had problem with a commercial tool before. But now i think about it, we had to restart it only after week-ends. Maybe the timeout is something like 24 hours or alike...
I was just noting this combinaison had no problems here. However, as long as store is still useable after that i have nothing against your suggested change ;). Of course, the fact 'it works here' does not mean you can't correct problems for those having problems! It's just you said default is to 8 hours and, as our DBA looked surprised when i asked for the idle connection timeout on the server, i concluded they never changed the default value and didn't even know it existed. Le Mardi 19 Avril 2005 14:32, Martin Kal�n a �crit : > delbd wrote: > > Here, we are using slide 2.1 with store on > > org.apache.slide.store.impl.rdbms.OracleRDBMSAdapter > > We have a max connection pool size of 5 for tests purpose (our db admin > > became crazy when we put a value of 50 and, due to some bug, tomcat was > > consuming those 50 connection, three times, making 150 session on oracle > > server). I never noticed any problem, though i let the test server run > > for about 3 days without restart. I didn't have to start it back in the > > morning and nobody was supposed to access it during the night. I'll try > > this afternoon to put it under stress so as to 'consume' the whole > > connection pool and see if anything happen after a night of sleeping. Am > > quite surprised i saw no problem for 5 months of developpement on an > > oracle connection if oracle store is so unsuable in production > > environnement. > > Note that the timeout setting for Oracle RDBMS to drop inactive connections > is configurable on the server-side. I would also assume that your DBA can > turn it off completely. > > However, it's quite common for many servers and IMO a usable setting as > connections idle >> several hours could be consuming valuable server > resources. > > Some installations have a limit on max connections and some even have to > pay license fees proportional to number of connections (somewhat stupid, > I know, since you can always proxy things in front of Oracle). > > I did not intend to say that Slide, Oracle or DBCP are unusable per se, > just that the combination of Slide+DBCP+Oracle will be unusable for many > production environments unless it's possible to configure DBCP better. > > If you disregard the fact that you have no problem with the validation > query in your particular environment, do you have any comments on the > proposed extended configuration? > > Regards, > Martin > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- David Delbecq Royal Meteorological Institute of Belgium --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
