Michael Edge wrote:
> Could anyone shed some light on what happens to the Cocoon connection pool when the
>database it depends on is shutdown and then restarted. I expect an exception to be
>thrown as the connections are invalid, and though I don't explicitly catch it using
>esql:error-results in my XSP page, I expect that this exception should appear
>somewhere; perhaps in a log file or returned as part of the XML generated by the XSP.
>However, if my database has been shutdown and then restarted, the XSP below returns
><tradingbook>Sorry, no trading book results!</tradingbook>. I have to restart Tomcat
>to get it working again.
<ot> please use carriage returns in your messages </ot>
The way the connection pooling works is that when the connections are set
with a specific Keep-Alive query that works, the connection will try to
be reestablished when the Keep-Alive fails. If the Pool cannot return
a valid connection, then it will throw an exception. You may experience
a long timeout while it is waiting to get a valid connection.
The ESQL logicsheet swollows *alot* of error messages. It is very possible
that ESQL is your problem.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
