Re: setTcpNoDelay; why not true by default?

Thanks, Scott. You understand what I've been trying to say. -- To unsubscribe, e-mail: For additional commands, e-mail:

Request Scope does not invalidate the session at the end of the request, long-lived sessions hang until timeout causing out-of-sessions error.

We did a test using Apache SOAP and Tomcat server. We set the session timeout to 15 minutes. We set number of sessions to 10 We set the scope of the deployed service to "Request" We ran a client connecting 20 times and got "Null pointer" exceptions after the 10th call. The log indicted that we

cvs commit: xml-soap/java/src/org/apache/soap/transport/http SOAPHTTPConnection.java

snichol 2002/07/30 13:32:05 Modified:java/docs changes.html java/src/org/apache/soap/transport/http SOAPHTTPConnection.java Log: Disable the Nagle algorithm on the client by default. This dramatically decreases latency when the payload is sma

Re: setTcpNoDelay; why not true by default?

OK, I've now confirmed that on a Windows 2000 server, there is a delayed ACK, so disabling Nagle on the client makes a difference. The error in my testing was that I was sending large payloads. With large payloads, the client has a full TCP segment (1460 bytes for Ethernet) to send after the HTT

cvs commit: xml-soap/java/src/org/apache/soap/transport/http Cookie.java

snichol 2002/07/30 11:46:38 Modified:java/src/org/apache/soap/transport/http Cookie.java Log: Use URL#getFile instead of URL#getPath, since the latter is not correct with JDK 1.3.x and later if the URL has a query string. Revision ChangesPath 1.3 +3 -3 xml-s

Re: what's wrong with my deploy

activation.jar is not being found by your servlet container. What container do you use? There are installation instructions for Tomcat, JRun, iPlanet, BEA and WebSphere. These include configuration changes to add the jars to the class loading chain. Scott Nichol - Original Message - F

Re: Apache SOAP and Axis

Most of the Apache SOAP developers moved to Axis a year ago, leading to, e.g., the one year gap between the release of 2.2 and 2.3. Products that integrated SOAP, such as WebSphere, will move to Axis. Certainly bug fixes will continue, but there will be a limit on the addition of new features.

Apache SOAP and Axis

With the emergence of Axis, does it mean that the Apache SOAP activities stop ? Thank you. Regards, Agustinus Tedja InfoDesign OSD -- To unsubscribe, e-mail: For additional commands, e-mail: