hello,

its me again with another jaybird/glassfish issue :) this one seems really
serious when using more than one firebird connection pool in one glassfish
domain. assume you have webapp webappA using jdbc ressource jdbc/aDB which in
turn uses connection pool poolA on databaseA. And another webapp webappB using
jdbc ressource jdbc/bDB on connection pool poolB using databaseB.
now the unthinkable happens: webappA and webappB get connections from both
connectionpools A and B! it seems completely random which webapp gets
connections from which database. i would not have believed this if i had not
seen it with my own eyes... same deployments work fine with oracle and mssql
databases. so i suspect jaybird is at fault here...

lutz