Sounds like a Tomcat bug.

Try Tomcat 4.0 Final (it's out). Also switch to jdk1.3.1+, we had nasty 
bugs running 1.3.0 + Soap2.2 on our RH host.

Laurent

Reply via email to