Looking at the bug report, it looks like this issue was resolved in Apache Tomcat 6.0.24. It doesn't show as closed. We did a preliminary test and appears it was fixed in 6.0.24, but we want to be absolutely certain, as the consequences are dire. Was this fixed for linux in 6.0.24 (and beyond)?
Thanks, Doug Fulford Software Engineering Specialist (626)812-2248
