That rings a bell, but not a very clear or loud one. I think we need to implement dispose or destroy or something like that on James.java (?) and various components...basically help Avalon do a graceful shutdown.
Glad the mordred stuff fixed things for you... I'm not sure if Berin has had time to make excalibur into a usable db pooler, but if not, maybe we can submit mordred back to the Avalon project. 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 11:56 AM Subject: RE: .. Bizzare ... (was feedback on the latset changes) > Aha! > You win the coconut! I was using an old one which specified excalibur, but > when I edited the config it changed to mordred, and all my troubles were > over. > > d. > > PS.. any idea why we get the "JVM terminating abnormally" and what is needed > to make it terminate "normally"? > > > -----Original Message----- > > From: Serge Knystautas [mailto:[EMAIL PROTECTED]] > > Sent: Monday, January 21, 2002 4:23 PM > > To: James Developers List > > Subject: Re: .. Bizzare ... (was feedback on the latset changes) > > > > > > Check your config.xml... that should define either > > org.apache.util.mordred.JdbcDataSource or the > > org.apache.avalon.excalibur.datasource.JdbcDataSource in the data-sources > > section. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
