Mailing-List: contact axis-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@xml.apache.org
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: Socket problems
Date: Tue, 30 Jul 2002 16:16:22 +0200
Message-ID: <21B200DF0688CC45ACF38F49D2279832297055@buebe002.NOE.Nokia.com>
Thread-Topic: "Chicken-Egg" problem with Java2WSDL/WSDL2Java
Thread-Index: AcI30glljzkm8GTuTz6M5057pi9UEwAAPjig
From: <Geza.Szocs@nokia.com>
To: <axis-user@xml.apache.org>, <axis-dev@xml.apache.org>

Hi,

  During a stability test with Axis, nightly build 2002-07-21 and Tomcat =
4.0.4.,
we experienced the following problem:=20
  We had a webservice deployed under Axis, which functioned
both as a SOAP server and a client. Meaning that it was capable of
receiving SOAP requests via HTTP, but also capable of
sending SOAP requests to other webservices, acting as a SOAP client=20
(using Axis client framework).
In both way our service was attacked with multiple threads, sending
around 30-40 requests/sec in both directions. We ecountered that
after a certain period of time (tipically 4-5 hours) the webserver
was not able to receive any more HTTP requests. However the client-side
was still sending SOAP requests to other servers. Analyzing with netstat
we found that around 2000 sockets have been created by Axis client=20
framework, which were still active, and this number didn't want to
decrease. It seemed like this client framework was eating up all =
resources
of the OS (sockets). I also checked to source code of HTTPSender, I see =
that socket
are not closed there. My question is, what happens to the created =
sockets ?
Does Axis leave everything to the garbage-collector, or are socket =
closed=20
later on by some handler ? When can the socket be closed and by whom ?=20

           Thanx in advance for your answers, Geza