On Sun, Jan 02, 2005 at 10:10:02AM +1100, Brett Randall wrote: : Yes, responsibility has been placed on developers and : architects, but a Tomcat admin who deploys : applications may not be in a position to hold them all : individually to account.
This is a policy/political problem, then, and not a technology issue. If developers push sloppy, cranky code into a production environment and they're not held accountable for the results, well... Options: 1/ replace the offending developers with people who understand and follow best practices. Supplement this crew with a rigorous testing/QA phase to smoke out any honest mistakes. (If this is a vended/third-party app, put pressure on the vendor.) 2/ Do a CVS pull and use/distribute your own "Thread-Cleanup Tomcat." (Sounds like you already know where to make your change.) 3/ Try to sway the Tomcat developers into folding #2 into the mainline code. (Good luck.) Should #3 pass, I suspect the next request would be for a "JDBC connection cleanup Tomcat" ;) -QM -- software -- http://www.brandxdev.net tech news -- http://www.RoarNetworX.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
