delbd wrote:
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.
OK, sounds like we agree. Thanks for your feedback!
The default Oracle timeout value might very well be ~24h and it might also
vary between different releases of Oracle server. My 8h mileage is just
based on empirical studies of x installations. (x=not-so-many) :)
You have a valid point when you say that it should work backwards-compatible
for the ones that did not (yet) have any problems with the default DBCP conf
in Slide.
I think this could easily be achieved by not specifying any of the new
configurable values in the Slide default Domain.xml (other than commented out
or otherwise disabled). This way the ones that need it (eg me!) can enable
it, and the rest will not notice any changes.
Although it's worth noting that the default DBCP settings in Slide are
"floating" at the moment, even if I don't touch them, since they are
dependent on the Commons DBCP and Commons Pool default values which
can (and have! [1]) change between releases. But they are at least
constant and deterministic for any given version of a Slide release.
Regards,
Martin
[1] See eg http://issues.apache.org/bugzilla/show_bug.cgi?id=10969
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
