[
https://issues.apache.org/jira/browse/GERONIMO-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662373#action_12662373
]
Radim Kolar commented on GERONIMO-4222:
---------------------------------------
I did testing on PostgreSQL 8.2 and WAS CE 2.1.1.1. After PGSQL is restarted db
pool is unusable, there is no hang, but Geronimo never recovers from that
error. Trace dumps are like this.
javax.servlet.ServletException: org.postgresql.util.PSQLException: An I/O error
occured while sending to the backend.
org.apache.jasper.runtime.PageContextImpl.doHandlePageException(PageContextImpl.java:852)
org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:781)
org.apache.jsp.index_jsp._jspService(index_jsp.java:535)
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:369)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:342)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:267)
javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
same application running in tomcat 5.5.25 container fails only once after pgsql
is restarted, following requests are fine. Probably tomcat db pool can detect
failed connections to database and close them instead of recycling them to
application.
> Database pool unusable after database unavailable for awhile
> ------------------------------------------------------------
>
> Key: GERONIMO-4222
> URL: https://issues.apache.org/jira/browse/GERONIMO-4222
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Affects Versions: 2.0.2
> Environment: Red Hat Enterprise Linux Server v5.2
> WAS-CE v2.0.0.1, based on Geronimo v2.0.2
> Reporter: David Frahm
> Fix For: Wish List
>
> Attachments: before and after wasce restart.txt, stacktrace.txt
>
>
> I have frequent trouble with my database pool to an AS/400. The database is
> taken down every night for backup, and at least once a week the connection
> pool is unusable after the database comes back up. Restarting the connection
> pool makes everything work again.
> We are new to Geronimo/WAS-CE -- just this one app on one server -- so I
> don't have anything to compare to. However, we have had this same issue with
> a couple 1.x/1.1.x versions before we upgraded to v2. Also, there are
> several WebSphere (full WAS, not WAS-CE) apps that do not have this trouble.
> Configuration Info
> Driver: JTOpen v6.1 (com.ibm.as400.access.AS400JDBCDriver)
> Pool Min Size: 0
> Pool Max Size: 100
> Blocking Timeout: 5000
> Idle Timeout: 15
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
