I tried porting to 2.4.5 today with the same results. It looks like the at least the first database access succeeds, but once the exceptions start, I can't access the database anymore.
My MySQL setup works perfectly in 2.4.4.
One other strange thing... I keep seeing multiple "Creating XA Pool" messages in the log. Shouldn't I only see this once per pool? Perhaps this is related?
Same problem here. My application runs on JBoss 2.4.4 but on 2.4.5 I get (among others) the following database exception:
[INFO,XAPoolDataSource] Creating XA Pool
[ERROR,es_framework] com.xyz.es.applications.ir.server.EmployeeBean: Unable to load employee bean EmployeePK[dvID=14]
java.sql.SQLException: Closed Statement
My datasource definition in jboss.jcml:
Can someone help me (us) out?
Same trouble here. Changed from 2.4.5 RC2+MySQL (I think) to 2.4.5Final+MySQL (MM JDBC driver 2.0.13) and couldn't access the DB.
I actually tried to run 2.4.5 final, with the much older MM JDBC driver 2.0.4, and it started WORKING!!!
I don't know why though...
In other threads the same problem is discussed for Oracle drivers. As each submitter states that all worked fine in JBoss 2.4.4 (or even 2.4.5RC3) I'm not convinced that moving back to a flintstones-version of the mysql driver is a real solution. The release notes of 2.4.5 describe changes that have been made in the PreparedStatement code and that's where the exceptions are thrown.
I'd love to submit this (apparantly) JBoss bug but JBoss version 2.4.5 is not yet in the bug-product-list. I'm wondering if this version is considered stable by the JBoss people...
JBoss 2.4.6 solves the problem.