I do not know about w2k ws, but on NT workstation it is 10. The limit is not actually connections, I believe, but on the number of connections that can be queued. This is enforced within the TCP/IP stack.
Scott ----- Original Message ----- From: "Richard Bolen" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, April 22, 2002 10:43 Subject: RE: Heavy loads on SOAP RPC What is the upper limit for connections with a non-server version of the microsoft OS? I'm having some performance problems as well and I'm testing on Win2K workstation. How is this connection limit enforced? At the TCP/IP stack level or the socket level (or some other way)? Rich -----Original Message----- From: Tiago Fernandes Thomaz [mailto:[EMAIL PROTECTED]] Sent: Monday, April 22, 2002 10:23 To: '[EMAIL PROTECTED]' Subject: RE: Heavy loads on SOAP RPC That's must it, Scott! I'm running the process on a Microsoft Windows 2000 Workstation. Not on a Server OS version. I'll try to run on a HP-UNIX machine to check this problem out. Thanks a lot. Tiago Fernandes Thomaz -----Original Message----- From: Scott Nichol [mailto:[EMAIL PROTECTED]] Sent: segunda-feira, 22 de Abril de 2002 14:28 To: [EMAIL PROTECTED] Subject: Re: Heavy loads on SOAP RPC The parameter is used as the backlog parameter in java.net.ServerSocket. This is used as the parameter to the underlying socket call listen(). It is the number of outstanding requests that will be queued by the OS and/or TCP/IP stack. See my other posting re: your operating system. If you are using a non-server version of a Microsoft OS, you are stuck with a low number of connections. Scott ----- Original Message ----- From: "Tiago Fernandes Thomaz" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, April 22, 2002 9:18 AM Subject: RE: Heavy loads on SOAP RPC > It seems that the conf parameter you sugested, > > <Parameter name="backlog" value="100"/> > > doesn't change anything. I got exactly the same number of exceptions. > Could you tell what this parameter is supposed to do? > Thanks. > > Tiago Fernandes Thomaz > > -----Original Message----- > From: Scott Nichol [mailto:[EMAIL PROTECTED]] > Sent: segunda-feira, 22 de Abril de 2002 13:09 > To: [EMAIL PROTECTED] > Subject: Re: Heavy loads on SOAP RPC > > > The Web server and/or servlet container against which you are testing > probably > has a limit set for the number of connections it will queue. In Tomcat > 3.2.1, > for example, server.xml has the "backlog" parameter for a Connector: > > <!-- Normal HTTP --> > <Connector className="org.apache.tomcat.service.PoolTcpConnector"> > <Parameter name="handler" > > value="org.apache.tomcat.service.http.HttpConnectionHandler"/> > <Parameter name="port" > value="8080"/> > <Parameter name="backlog" value="100"/> > </Connector> > > In Tomcat 4.0.1, the Connector has an acceptCount attribute: > > <!-- Define a non-SSL HTTP/1.1 Connector on port 8080 --> > <Connector className="org.apache.catalina.connector.http.HttpConnector" > port="8080" minProcessors="5" maxProcessors="75" > enableLookups="true" redirectPort="8443" > acceptCount="10" debug="0" connectionTimeout="60000"/> > > Scott Nichol > > ----- Original Message ----- > From: "Tiago Fernandes Thomaz" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Monday, April 22, 2002 5:58 AM > Subject: Heavy loads on SOAP RPC > > > > Hi, > > > > I'm facing some trouble concerning heavy loads on soap rpc. > > I coded a soap client that simulates several clients with a Thread > > implementation. > > My snippet code is: > > > > public class SOAPClient > > { > > public static void main (String[] args) throws Exception > > { > > URL url = new URL(args[0]); > > String sXML = null; > > > > for (int i = 0; i < 50; i++) > > { > > sXML = "<?xml version=\"1.0\" encoding=\"US-ASCII\"?><request > client > > = \"client"+i+"\" action = \"action"+i+"\"><parameter name = > > \"name"+i+"\">My Name"+i+"</parameter></request> "; > > > > Call call = new Call(); > > call.setTargetObjectURI("urn:Connector"); > > call.setMethodName("sendRequest"); > > > call.setEncodingStyleURI("http://schemas.xmlsoap.org/soap/encoding/";); > > Vector params = new Vector(); > > params.addElement(new org.apache.soap.rpc.Parameter("sXML", > > String.class, sXML, null)); > > > > call.setParams(params); > > > > (new TestThread(call, url)).start(); > > } > > } > > } > > > > > > public class TestThread extends Thread > > { > > Call testCall = null; > > URL url = null; > > > > public TestThread(Call testCall, URL url) > > { > > this.testCall = testCall; > > this.url = url; > > } > > > > public void run() > > { > > try { > > org.apache.soap.rpc.Response resp = testCall.invoke(url, ""); > > > > if (resp.generatedFault()) > > { > > Fault fault = resp.getFault(); > > System.out.println(this.getName() + "Fault Code = " + > > fault.getFaultCode()); > > System.out.println(this.getName() + "Fault String = " + > > fault.getFaultString()); > > } > > else > > { > > org.apache.soap.rpc.Parameter result = resp.getReturnValue(); > > String res = result.toString(); > > Object obj = result.getValue(); > > String resp2 = obj.toString(); > > System.out.println(this.getName()+" - Result: "+resp2); > > } > > } > > catch (Exception e) > > { > > System.out.println(this.getName() + " :Error! - " + e.getMessage()); > > } > > } > > } > > > > , and I'm getting the following exception for most of the Threads (30 out > of > > 50): > > > > Thread-i Error opening socket: Connection refused: connect > > > > Does anyone explain me why am I getting this? Is it because SOAP can only > > handle about 20 http connections? > > > > Tiago Fernandes Thomaz > > >
