> I really like to go to jboss 3.2.6+jaybird because of performance
> issues but it has to run stable. For now I switched back to
> Interclient which is old but works stable.

If you can live with InterClient, you should be also ok running JayBird as
normal JDBC driver, not a JCA connector. Use the InterClient's datasource
configuration, just replace the JDBC driver name and connection URL.

The error you see has something to do with the JBoss (it is not able to
delist connection from the transaction), at least I do not see anything from
JayBird in your stack trace (except that it could not obtain managed
connection from JBoss).

Roman