thanks, I saw that and I think that issue is in reference to the original code using Spring to init the datasource. Someone mentions that here: http://stackoverflow.com/questions/14711073/deploying-grails-war-on-jetty-gives-concurrentmodificationexception
We don't init the actual datasource in Spring at all. we do a call in Java: BasicDataSource dataSource = new BasicDataSource(); whenever a new connection needs to be made. I wonder if anyone here has noticed this before since it is quite strange. Also can you explain what the logwriter daemon thread is any why it sticks around after I close my last connection? On Monday, 7 October 2013 10:08:06 UTC-4, Noel Grandin wrote: > > I have no idea why this is happening, but it does not appear to be H2 > specific: > > > http://www.mkyong.com/websphere/basicdatasource-causing-java-util-concurrentmodificationexception-in-websphere/ > > > On 2013-10-04 20:23, Jonathan Stevens wrote: > > Caused by: java.util.ConcurrentModificationException > at java.util.ArrayList$ArrayListIterator.next(ArrayList.java:569) > at java.sql.DriverManager.getDrivers(DriverManager.java:258) > > > -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/groups/opt_out.
