Hi Thomas, It seems the watchdog dictates when the exceptions get thrown. In my application, I'm reading in a large file and for every line in the file, I'm transforming the line and inserting records into an embedded database. So, part way through this rather long file, the watchdog closes the connections en masse, so I get a large number of simultaneous stack traces; all the while the application still parses and inserts records. As far as that goes, there is no corruption of the data stream, which is good. My concern is whether I'm dealing with the data source correctly or if I need to do more up-front work in setting up the connection pool.
In my app, I create an H2DataSourceFactory that sets up the jndi initial context (I'm running this standalone and not in a container). I use a separate DbConnectionFactory to deal out connections from the registered datasources. So, my DbConnectionFactory first initializes the H2DataSourceFactory and then dispatches connections. Since the H2 jdbc library doesn't specifically have a PooledDataSource, I'm assuming that calling getPooledConnection.getConnection() from the JdbcDataSource reference will do that work for me. Perhaps this is my mistake? I haven't checked the source yet to see whether that's the case. Btw, I'm not specifically creating an H2 database connection pool, because I want to remain agnostic to the data sources registered in my DbConnectionFactory. Basically, I'm hand-bombing a DI layer. Thanks, Robin. -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To view this discussion on the web visit https://groups.google.com/d/msg/h2-database/-/jHzj91HFh2cJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
