Hi Danny, sorry if this is not what you have been asking for, but it looks like eiter a keep alive or connection check. In mysql 'select 1' is a legal sql statement. I don't know if this is the reason, but mysql connections get regularly broken (other than for example oracle connections, in which I suppose the reconnect happens transparent to the jdbc client software). Thus, it would make sense to check a connection before taking it from the pool. Cheers, Marcus
> -----Original Message----- > From: Danny Angus [mailto:[EMAIL PROTECTED]] > Sent: Monday, January 21, 2002 3:42 PM > To: James Developers List > Subject: .. Bizzare ... (was feedback on the latset changes) > > > I re-wrote my config.xml file from the "clean copy" and all my > JDBCRepository connection errors have dissappeared, even though there > appears to be no diff between the old and new conf. > > Hmm.. put it down to experience. > > Anyway .. > > watching the db log there seems to be a better quality of > pooling going on, > everything is using the same connection id (I haven't got the > load for more > than one) > > However I keep seeing this in the log.. > 020121 14:29:07 115 Query SELECT 1 > 115 Query SELECT message_name, > message_state, > last_updated FROM message WHERE repository_name = 'spool' ORDER BY > last_updated ASC > > And what I want to know is; Where does "SELECT 1" come from? > > d. > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
