My application does not use direct jdbc calls and all EJBs are CMT CMP20 beans. I use PostgreSQL. I see that all unused connections in jboss pool are marked by postgres as "idle in transaction". It means jboss does not end the JDBC transaction properly (although all changes are saved correctly and I have no problems with the application itself). This behaviour prevents me from running VACUUM, CREATE/DROP INDEX and other commands requiring table lock. I've found a related thread in this list where one explained this issue so that a connection is not associated with XA connection or something but in my case jboss manages everything... Can I have couple of ideas? I use jboss 3.0.6 and the standard configuration (no jboss.xml in the application and jbosscmp-jdbc.xml only overrides default datasource type and couple of finders).
------------------------------------------------------- This SF.net email is sponsored by:Crypto Challenge is now open! Get cracking and register here for some mind boggling fun and the chance of winning an Apple iPod: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
