geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Forrest Xia (JIRA)" <>
Subject [jira] Commented: (GERONIMO-4222) Database pool unusable after database unavailable for awhile
Date Tue, 21 Jul 2009 15:15:14 GMT


Forrest Xia commented on GERONIMO-4222:

Does some testing on this issue. Conclude that:
1. tranql-connector-postgresql-xa adapter has no such problem.
2. tranql-connector-postgresql-local does have such problem

Besides the exception described by Radim Kolar, additional exceptions are:
Caused by: Broken pipe
	at Method)
	at org.postgresql.core.PGStream.flush(
	at org.postgresql.core.v3.QueryExecutorImpl.sendSync(
	at org.postgresql.core.v3.QueryExecutorImpl.execute(
	... 62 more

Seems for local transaction db pool of Postgresql, the bad connection won't be threw out,
for following db request, the server still return the bad connection to application.

But for XA transaction db pool of Postgresql, no such problem.

> Database pool unusable after database unavailable for awhile
> ------------------------------------------------------------
>                 Key: GERONIMO-4222
>                 URL:
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>    Affects Versions: 2.0.2, 2.1.3, 2.1.4
>         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 (
> 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.

View raw message