- Posted by: praveen simlote
- Posted on: June 29 2001 01:35 EDT
we are using connection pooling with Sql Server 7.0.my entries in weblogic.properties file are
when all 3 connections are busy andif a request comes then it should ideally wait for connection instead of that it throws weblogic.ResourceNotAvailable.
can anyone help??
Thanks in advance
We came accross problems with this on a previous project when using the dev version of the JDBC driver which was limited to 3 connections. You can either just wait till you have a deployment license and up the connection pool size or you could write a utility class that gets connections from the pool and basically does -
try to get connection
if noresourceException caught wait then try again
up until some maximum timeout.
At least by putting the exception handling in the helper class you don't tie you're bean to any specific weblogic classes.
Its a bit anoying really. I'm not sure if there is a speced way that connection pools should behave when they have no connections left. I don't know if all servers tend to throw an exception of some sort or whether some will just wait.