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=6048>. 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=6048 JDBC pool unavailable while using WARP connector Summary: JDBC pool unavailable while using WARP connector Product: Tomcat 4 Version: 4.0.1 Final Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: Normal Priority: Other Component: WARP Connector AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I've just encountered a problem with usage of JDBC pool defined in both server.xml and WEB-INF/web.xml while trying to access the application via WARP. When I test it without WARP it works great but after deployment in production env. it cannot get DataSource object from context. I've tried version 1.0 and 1.0.1 of WARP with the same effect. Now I have changed the code back to use direct JDBC connection so there is no URL to show the error message but it wasn't really helpfull. My application is deployed on one of the virtual hosts and thus the context suffix in URL changes (actually it disappears - the app is available from / of the virtual host). -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
