It looks like the org.jboss.mq.pm.jdbc2.PersistenceManager on JBoss 3.2 is not closing a database connection when it fails to create the desired tables. It is then causing an ugly warning message every time JBoss starts up.

This is from my log file:

2003-04-22 15:40:46,352 DEBUG [org.jboss.mq.pm.jdbc2.PersistenceManager] Could not create table with SQL: CREATE TABLE JMS_MESSAGES ( MESSAGEID INTEGER NOT NULL, DESTINATION VARCHAR(255) NOT NULL, TXID INTEGER, TXOP CHAR(1), MESSAGEBLOB OBJECT, PRIMARY KEY (MESSAGEID, DESTINATION) ), got : java.sql.SQLException: Table already exists: JMS_MESSAGES in statement [CREATE TABLE JMS_MESSAGES ( MESSAGEID INTEGER NOT NULL, DESTINATION VARCHAR(255) NOT NULL, TXID INTEGER, TXOP CHAR(1), MESSAGEBLOB OBJECT, PRIMARY KEY (MESSAGEID, DESTINATION) )]
2003-04-22 15:40:46,352 DEBUG [org.jboss.mq.pm.jdbc2.PersistenceManager] Could not create table with SQL: CREATE TABLE JMS_TRANSACTIONS ( TXID INTEGER ), got : java.sql.SQLException: Table already exists: JMS_TRANSACTIONS in statement [CREATE TABLE JMS_TRANSACTIONS ( TXID INTEGER )]
2003-04-22 15:40:46,372 WARN [org.jboss.resource.adapter.jdbc.WrappedConnection] Closing a statement you left open, please do your own housekeeping
2003-04-22 15:40:46,372 WARN [org.jboss.resource.adapter.jdbc.WrappedConnection] Closing a statement you left open, please do your own housekeeping
2003-04-22 15:40:46,372 INFO [org.jboss.mq.pm.jdbc2.PersistenceManager] Started

Anybody know if this is being addressed in an upcoming release?