This content has been marked as final. Show 3 replies
I have pinpointed the problem to the fact that when I make a call to a stored procedure and the stored proc raises an exception (data not found), my createSQL statement also raises an error (as I want it to).
However, the VB error handling code contains a call to OraDatabase.RemoveFromPool that does not work. It gets executed, but pool current size is not decremented as it should be. Again, any information is appreciated. Thanks.
Unfortunately, no one replied to my post :-(, but I did solve the problem and I am posting the solution in case someone else faces the same problem.
I wrapped the code where I get a connection in a subroutine. In that subroutine, I first check if there is an active connection already and if so, I just exit. If not, I get/open a connection. Thanks.
I realize that this is an old post and i hope you get this message. how do you check for an open connection in your subroutine im having the same problem...