> From: cjder...@gmail.com [mailto:cjder...@gmail.com] On Behalf Of chris derham
> Subject: Re: Connection pool race condition
> Fixed this by setting the service to startup delayed
> sc config start= delayed-auto
Sounds like a FAQ/Wiki entry might be in order here, but I'
Fixed this by setting the service to startup delayed
sc config start= delayed-auto
Thanks
Chris
There is another solution that should work, and that is to define initialSize="0" so that no attempt is made to contact the DB when it is
created. Then set testOnBorrow="true"
The jdbc-pool project should work like this
http://people.apache.org/~fhanik/jdbc-pool/
Filip
On 4/28/2011 1:58 PM, Fi
this is the way to go, just setup a service dependency
On 4/28/2011 7:36 AM, Peter Crowther wrote:
You could use Windows' service dependency management (
http://support.microsoft.com/kb/193888) to start Tomcat only after Oracle
reports that it's running. This might still cause problems if Ora
On 4/28/2011 8:36 AM, Peter Crowther wrote:
You could use Windows' service dependency management (
http://support.microsoft.com/kb/193888) to start Tomcat only after Oracle
reports that it's running. This might still cause problems if Oracle does
the same as SQL Server and continues recovering a
You could use Windows' service dependency management (
http://support.microsoft.com/kb/193888) to start Tomcat only after Oracle
reports that it's running. This might still cause problems if Oracle does
the same as SQL Server and continues recovering after its "official" startup
has finished. In
