Hi,

> we are using a Firebird 1.0 server runnning on Sun Solaris and a web
> application running on a Tomcat (4.1.27 ) on SuSe-Linux (9.0).
> We configured two jdbc connection pools in Tomcat to connect to the
> Firebird databases "A" and "B" on one server. When switching the web
> application from connection pool "A" to "B" we got the following
> exception when using a connection from pool "B":
>
> 16.12.2003 18:30:00:061 Exception in Database.executeQuery(select *
> from ...): java.sql.SQLException: ResourceException:
> org.firebirdsql.jca.FBResourceException: internal gds software
> consistency check (next transaction older than oldest active
> transaction (266))
> Reason: internal gds software consistency check (next transaction
> older than oldest active transaction (266))

Seems to be something wrong with the database. But if you believe that
everything is ok, a test case to reproduce the problem would be great.
It might be that somehow (should never happen) we send incorrect
transaction handle to the database "B" and this causes this error
instead of reporting something like "incorrect tx handle"...

> From that time we got a lot of exceptions like this until we restart
> the Tomcat:
> 16.12.2003 18:45:01:400 Exception in Database.executeQuery(select *
> from ...): java.sql.SQLException: ResourceException:
> org.firebirdsql.jca.FBResourceException: local transaction active:
> can't begin another
> Reason: local transaction active: can't begin another

This should happen after some another exception. Can you post that
another exception here?

Thanks!
Roman