Dear all, i've been using the apache SOAP distribution alongside tomcat 3.3 milestone 2 and believe i have found a problem within tomcat. after making several requests (3 actually) the 4th request fails and the SOAP code sits waiting to read the request even though the SOAP client has sent the data. on debugging the code i found that the org.apache.tomcat.facade.HttpServletRequestFacade is returning an already constructed Reader on a call to getReader(). if i set the member variable reader to null in recycle() then everything works fine. has anyone had a similar problem, or can they comment on whether this is just something odd with the SOAP + tomcat 3.3m2 combination? if you require more information or the patched code to look at just drop me a line and i'll send what i can. Cheers, Matt ----------------------------------------------------------------------------- Sessami is a trademark of Escape Velocity Technology Mobile Services Limited. All information contained in this e-mail is confidential and for the use of the addressee only. If you receive this message in error please notify.
