l
> > 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
g 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 *
ould 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
Hi.
although it seems to be only me who is bitten by a wrong startup order
I have investigated the problem a bit further. The actual order in
which components are initialized seems to be more or less random, based
on the hash values computed in
org.apache.avalon.excalibur.collections.BucketMap
