Bugs item #995099, was opened at 2004-07-21 09:22 Message generated for change (Comment added) made by ejort You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=995099&group_id=22866
>Category: JBossCX Group: v3.2 Status: Open >Resolution: Accepted Priority: 5 Submitted By: Dmitry Shohov (shohou) >Assigned to: Adrian Brock (ejort) Summary: ConcurrentModificationException with not closed PreparedStat Initial Comment: I'm using jboss v3.2.6RC1 and getting ConcurrentModificationException when more than one PreparedStatement not closed. Exception occurs in method Connection.close(). I know that I must close PreparedStatements, but I think it is the bug anyway. Problem exists only in v3.2.6RC1, in v3.2.5 that works without any exceptions. OS - Win2000 JDK Version - j2sdk1.4.2_04 ---------------------------------------------------------------------- >Comment By: Adrian Brock (ejort) Date: 2004-07-21 12:33 Message: Logged In: YES user_id=9459 The change made in 3.2.6RC1 is that you don't have to explicity close statements :-) http://www.jboss.org/wiki/Wiki.jsp?page=ConfigDataSources You can get the 3.2.5 behaviour by adding <track-statements>false</track-statements> to the -ds.xml It looks like the problem you report has been around in all 3.2.x versions. I will fix it. e.g. try 3.2.5 with <track-statements/> in your -ds.xml ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=995099&group_id=22866 ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
