Hi Bernard,

Very little bandwidth is used. Most persistent connection pooling code is
set up to send out a validation query periodically to keep the server from
dropping the connection. How often it does that can usually be specified by
you to conform with whatever the timeout is on your database server.

Most timeouts are on the order of 15-30 minutes so this validation query
only needs to be sent out a few times per hour per connection.

So the overhead is negligible even for large numbers of connections.

During setup of your persistent pooling software you may be required to
enter an sql connection validation query to be used for this "tickle".

A good one for Firebird is:

SELECT CAST(1 AS INTEGER) FROM rdb$database

This select will always succeed if the connection is still alive and will
have exactly one row in the result set.

Hope this helps,

Rick

----- Original Message -----
Subject: [Firebird-Java] persistent connections


> I want to start using persistent pooled JDBC connections. Do such
> connections use up much bandwidth when there is not data being
> transmitted? It would be useful for me in designing my architecture
> to know how much bandwidth is being utilised when such a connection is
> idle.
>
> Thanks
> Bernard
>