Are you using the Excalibur code, or at you using the James-specific 'mordred' code? I had hacked the mordred stuff together since excalibur wasn't reliable and I became desperate to upgrade. Namely, 1. It had little or no error feedback if there was trouble setting up the DB. 2. It automatically killed a connection after 15 uses 3. The pooling was unreliable about creating new connections when needed (although the kill-on-15 rule would mask most of these issues)
Unless you've changed this in James, the db and dbfile repositories are using my db pooling/resource hack. Just thought I'd mention if you're trying to track down the problem... Serge Knystautas Loki Technologies - Unstoppable Websites http://www.lokitech.com/ ----- Original Message ----- From: "Danny Angus" <[EMAIL PROTECTED]> To: "James Developers List" <[EMAIL PROTECTED]> Sent: Monday, January 21, 2002 9:42 AM 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]>
