> From: Christian Haul [mailto:[EMAIL PROTECTED]] > > On 14.Mar.2002 -- 09:14 AM, Carsten Ziegeler wrote: > > Hi Team, > > > > let's try to get closer to the "release often, release early" theme. > > > > Vadim and I propose to make a code freeze now or feature stop now > > and make a "bug fix/doc update" phase for some time (one week or so) > > and then release a new version. > > > > So, please state your opinion. > > Carsten, > +1 but one serious problem should be fixed first: since the HSQLDB server > is made a avalon component but never used as such, it is not guaranteed > that it is started before a connection is attempted to it.
Chris, The more I think about issue you found... The more I'm sure that the problem is not in the order (also I agree - sometimes order could be of importance), but in the way how JDBC pool is being created. I think pool should be more resilient to the temporary network issues, and it should try to create connections, till success, with some time interval. Common example of why this is required: if tomcat and Oracle are started on the same machine as services, and *even* if you have correct service startup order (tomcat depends on oracle), still tomcat will come up before than oracle mounts its database. If this is installed on different machines though, the requirement to have self-healing pools is even more important. What do you think? Vadim > > It looks like I am the only one who has (knowingly) experienced this > problem but it has been sheer luck that it is not more widespread. > Although on identifying the problem I have dived into the startup code, > I don't know enough to come up with a good solution for this. > > Chris. > > -- > C h r i s t i a n H a u l > [EMAIL PROTECTED] > fingerprint: 99B0 1D9D 7919 644A 4837 7D73 FEF9 6856 335A 9E08 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
