This is a really bad bug... I just spent all day trying to upgrade to tomcat5.5 to be bitten by this. Looking forward to the official fix, but in the meantime I've used the workaround mentioned here.
This is a really bad bug... I just spent all day trying to upgrade to tomcat5.5 to be bitten by this. Looking forward to the official fix, but in the meantime I've used the workaround mentioned here.