Yes I had the same problem. To go around this specific one, since my store
procedure takes some time to execute, I create a "fresh" connection for it only and
close on the return. Also, on my case the user doesn't need to know the result, so
I out.close() before I call the store procedure.
I think it is not caused by the "dbconnection", but the jdbc driver. (i am guessing
you are using oracle ?). For the oracle jdbc (in particular), it is very important
to close resultset and statement (on this case CallableStatement). My guess is that
on some cases, the store procedure is openning something and not closing properly.
I also found out that the first store procedure call works fine, but any other
call using the same connection won't work.....
Rodrigo
"Daniel Vontobel [EMAIL PROTECTED]" wrote:
> hello there
> i use dbconnection too... but i have some trouble.
> in my application the dbclasses get a connection from the pool,
> then they call a stored procedure and return the connection to the pool.
> this works fine until the stored procedures returns a resultset. but
> i have insert or update-sp that don't return a resultset. the next time i
> use this connection from the pool, i always get an odbc-exception
> "connection is busy". i tried different ways to execute the stored
> procedure.
> the only workaround i've found till now is to "kill" the connection in the
> pool and
> get a new one.
>
> does someone have any clue?
> thanks
> Sandro
>
> ===========================================================================
> To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
> FAQs on JSP can be found at:
> http://java.sun.com/products/jsp/faq.html
> http://www.esperanto.org.nz/jsp/jspfaq.html
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
FAQs on JSP can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
