Subject | Connection pool and remaining fb_inet_server processes |
---|---|
Author | Yves Glodt |
Post date | 2008-12-18T12:26Z |
Hello,
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
- netstat -t | /bin/grep gds shows just a small amount of connections
- Even after stopping tomcat the fb_inet_server processes stay there
How can I be sure my pool is not causing this...?
I have noticed that some people use org.firebirdsql.pool.FBWrappingDataSource
as a driverClass. What is the difference?
Best regards,
Yves
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
- netstat -t | /bin/grep gds shows just a small amount of connections
- Even after stopping tomcat the fb_inet_server processes stay there
How can I be sure my pool is not causing this...?
I have noticed that some people use org.firebirdsql.pool.FBWrappingDataSource
as a driverClass. What is the difference?
Best regards,
Yves