On Thursday 18 December 2008, Roman Rokytskyy wrote:

> > I use a connection pool with tomcat 5.5/java 1.5 which is set up
> > like this:
> >
> > <Resource auth="Container"
> > driverClassName="org.firebirdsql.jdbc.FBDriver" maxActive="50"
> > maxIdle="5" maxWait="5000" name="jdbc/Prod" password="masterkey"
> > type="javax.sql.DataSource"
> > url="jdbc:firebirdsql:server2003:db?encoding=ISO8859_1"
> > username="SYSDBA" validationQuery="select 1 from RDB$DATABASE" />
> >
> > It runs on a debian etch server and connects to a windows 2003
> > server, and we have a lot of fb_inet_server processes which do not
> > disappear... More info
>
> Can it be that Tomcat opens at minimum 10 connections on start? There
> should be a property to control this.
>
> > - netstat -t | /bin/grep gds shows just a small amount of
> > connections - Even after stopping tomcat the fb_inet_server
> > processes stay there
>
> That is strange... I would suspect that it has something to do with
> the network configuration. Try opening a new isql session to your
> win2k3 server, you should get a new process there, then close the
> session and check whether the process is gone. If not, then this is
> config issue with your win2k3 server, if yes - with pool.

Hi Roman and list, sorry for late answer. The problem has been identified
as a networking issue. The firewall is killing inactive connections after
some hours. Somehow the validation query does not make them look
"alive"... We are still investigating on that

Thanks for your suggestions and best regards!
Yves

> > I have noticed that some people use
> > org.firebirdsql.pool.FBWrappingDataSource as a driverClass. What is
> > the difference?
>
> I would wonder if it works as driver class. It is a full
> implementation of a connection pool and implements
> javax.sql.DataSource interface.

It doesn't, was rubbish I told... sorry

> Roman

[Non-text portions of this message have been removed]