[
https://issues.apache.org/jira/browse/GERONIMO-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jencks updated GERONIMO-4222:
-----------------------------------
Fix Version/s: (was: 2.1.5)
(was: 2.2)
Wish List
If someone were to investigate this issue they need to look into whether some
of these are not working:
- in geronimo connection management, if a fatal error occurs then the managed
connection should get destroyed and removed from the pool. The user app will
get an exception, and it should do something to deal with it. For instance, it
could ask the user to retry later, or it could try again with a new connection.
- The tranql postgres wrapper needs to tell geronimo that a fatal error
occurred by calling (IIIRC) a connectionErrorOccurred with an event. If this
is not happening then the tranql wrapper needs to be taught how to recognize
fatal errors.
-- Note also that anyone using the generic wrapper wont get very reasonable
behavior because there is no standard way to tell that an SQLException means
the connection is dead.
I don't see anyone fixing this right now so it wont be in 2.2
> 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, 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 (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.
