DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13177>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13177 pingquery behaviour changed after switching to commons-dbcp Summary: pingquery behaviour changed after switching to commons- dbcp Product: Struts Version: Nightly Build Platform: All OS/Version: All Status: NEW Severity: Minor Priority: Other Component: Utilities AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Can you add this to the documentation of the data-sources configuration: When GenericDataSource implemented a connectionpool itself, it's pingquery property required a valid sql statement. Since GenericDataSource is turned into a wrapper for commons-dbcp BasicDataSource, it's pingquery property requires an sql statement that must return at least one row. If you provide a valid sql statement that does not return data, your program gets locked in loop when you try to retrieve the first connection. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
