Starting weblogic while the database is down.

Question

We encountered a problem starting weblogic 8.1.5 while the DB is down.
The problem is that the connection pool fails to be created. The DS fails to be created as a result.
When the DB finally comes up, the connection pool does not recover although it does test upon reservation.
The only way I was able to recover the pool is by undeploying it from the server and then redeploying it. Even then, the DS did not recover; I had to undeploy it and then redeploy to achieve the full recovery.
I have found a question about this issue from 4 years ago and the suggestion was to create the connection pool with initial size of 0. That won't work for us.
Any Ideas?
Oded Blayer
Invoke Solutions
[email protected]

Answer 1

Oded Blayer wrote:
Thanks for the rapid reply.
The application is in production stage, and such configuration change requires time to make sure the performance is not harmed.
The dynamic creation will require even deeper changes.
Will this issue solved in later versions of weblogic (9, 10)?
Oded Blayer
Invoke SolutionsThe connection retry, init-cap=0, and dynamic pool creation
will probably be the only options for the near future,
and any new option would be to simply allow the pool to
come up with no connections, and would then act exactly
as if you'd set init-cap=0 anyway.
For your current case, connection retry or init-cap=0
are probably the most appropriate. Retry will make connections
soon after the DBMS is available, whereas init-cap=0 will
populate the pool as application load requires it. The
performance will only be affected for the first application
sessions, and will be hurt only by the amount of time it takes
to make a real DBMS connection. Do not alter the capacity increment.
Leave it at 1.
Joe