cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Haul <>
Subject Re: "startup order", was: [Vote]: New Release
Date Thu, 14 Mar 2002 15:27:04 GMT
On 14.Mar.2002 -- 09:26 AM, Vadim Gritsenko wrote:
> > From: Christian Haul []

> > +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, I admit that my concern is quite short sighted :-) Actually, I
_believe_ Avalon's Connection Pools do reconnect if for some reason or
other connections are lost. But they don't like that to happen on
startup. Failing early is a good concept because it eases bug hunting.
If not for this reason one might want to ask why connect to the DB
before a connection is requested anyways? So I wouldn't go for repeated
tries to connect but connect as late as possible.

Unattended server starts are definately an issue.

So, shall we escallate this issue to avalon-dev, then?

BTW ExcaliburComponentManger does some good magic to initialize
components in correct order. Can't know about HSQLDB, though.


C h r i s t i a n       H a u l
    fingerprint: 99B0 1D9D 7919 644A 4837  7D73 FEF9 6856 335A 9E08

To unsubscribe, e-mail:
For additional commands, email:

View raw message