Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.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: ThreadLocal Call objects using in a servlet memory leak ?
Date: Fri, 27 Jun 2003 14:43:39 -0400
Message-ID: <0B28D7F18975964A85394D5762C76A52047406B6@CATL0MS03.corp.cox.com>
Thread-Topic: ThreadLocal Call objects using in a servlet memory leak ?
Thread-Index: AcM83AMnZ8WIsk5dQ0+zOYDT5QKCng==
From: "Jackson, Jen (CCI-Atlanta)" <Jen.Jackson@cox.com>
To: <axis-dev@ws.apache.org>,
	<axis-user@ws.apache.org>

Has anyone else noticed that if you create an =
org.apache.axis.client.Call in a servlet in tomcat, it consumes a thread =
and never dies?  I seem to think this is because of the ThreadLocal =
references throughout the classes.  Is there something we can do to =
avoid this?  I am only following the documentation on how to use it, and =
calling the generated code from a servlet:


try {

  EdgeHealthPortType port =3D getService().getEdgeHealthPort();

  modem =3D (String) map.get(UsageKeys.MODEM_MAC_ADDRESS_KEY);

  //this is the generated function, which creates an =
org.apache.axis.client.Call object,
  //which gets somehow stuck in tomcat's threadpool forever.......
  usageToday =3D port.getModemCurrentUsage(modem);

=20
 =20
}=20
catch (javax.xml.rpc.ServiceException se) {
    throwError(
    modem,
    se,
    UsageKeys.ERROR_CURRENT_USAGE_NOT_AVAILABLE_KEY);
}=20
catch (java.rmi.RemoteException re) {
    throwError(
    modem,
    re,
    UsageKeys.ERROR_CURRENT_USAGE_NOT_AVAILABLE_KEY);
}


And ideas?  Anyone else experience this?  I used Jprofiler to diagnose =
this. =20


Jennifer Jackson
Programmer/Analyst