Le 06/02/16 20:53, Jan Sindberg a écrit : > When an application such as Fortress Commander is left inactive for hours - > all connections in the connection pool is closed (timed out ?). But for > each connection there is a 30 sec. This is the default LDAP API timeout. This is configurable.
> timeout before the conclusion that the > connection is dead. With 10 connections that is a five minutes wait for the > first "unknowing victim" and an application-log with ten equal logs > including stack trace. > How are you dealing with this in your systems? > Can I configure this differently from Fortress or in ApacheDS? > Could we make Fortress be a little faster realising that the connection > pool needs to be "refreshed"? > I guess the issue could be simulated by restarting ApacheDS (I haven't > tested this yet) - that should break whatever open connections there we. We can improve the way the pool detect dead connections.
