Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (nike.apache.org: domain of CEmerson@orangelake.com
 designates 208.84.181.7 as permitted sender)
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Please help ... [MultiThreadedHttpConnectionManager cleanup]
Date: Sat, 27 Nov 2010 09:51:20 -0500
Message-ID: <D1A110F4E3FD764FADDA40E2D3A29BA5D1F7C1@olex08.olcc.lan>
In-Reply-To: <4CF10E09.5090306@christopherschultz.net>
Thread-Topic: Please help ... [MultiThreadedHttpConnectionManager cleanup]
thread-index: AcuOOvWIr9I1RXloQjueHKu0SUHgDQABtEJg
References: <D1A110F4E3FD764FADDA40E2D3A29BA5D1F7A8@olex08.olcc.lan>
 <6D8F0A4A19FB2A49815191AC1C2B128E09ED34BF@UKEXCHANGE1.Europe.iSOFTGroup.co.uk>
 <4CED2594.4000003@pidster.com> <4CF10E09.5090306@christopherschultz.net>
Importance: normal
Priority: normal
From: "Emerson, Christopher" <CEmerson@orangelake.com>
To: "Tomcat Users List" <users@tomcat.apache.org>

That scares me a little bit.  If I have 100+ concurrent users, won't
that effect the other users?

I've gone through every blog, jira, axis2 documentation site in the past
4 weeks and I've tried writing the client many ways with no luck so I
was pretty sure I am closing down the client the way I am supposed to.

Is it possible that I have something as simple as an incorrect web.xml
configuration?

Another thing I noticed is that the servlet api is in Tomcat's lib
directory.  Should that be in the individual webapp directories?

-----Original Message-----
From: Christopher Schultz [mailto:chris@christopherschultz.net]=20
Sent: Saturday, November 27, 2010 8:56 AM
To: Tomcat Users List
Subject: Re: Please help ... [MultiThreadedHttpConnectionManager
cleanup]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Chris,

On 11/24/2010 9:47 AM, Pid wrote:
> SEVERE: A web application appears to have started a thread named
> [MultiThreadedHttpConnectionManager cleanup] but has failed to stop
it.
> This is very likely to create a memory leak.
>=20
> MultiThreadedHttpConnectionManager is a class from HTTP Client.

If you are using Axis and it's creating a
MultiThreadedHttpConnectionManager, it should be stopping it when the
webapp undeploys.

So, the question is: are you properly shutting-down the Axis services
when your webapp shuts down? If you are, then this is a bug in Axis that
should be reported to them.

If you aren't, then you need to do so.

If you want a quick solution, you can always write your own
ServletContextListener and call
MultiThreadedHttpConnectionManager.shutdownAll() -- it's a static method
that looks like it'll kill all threads from all
MultiThreadedHttpConnectionManager objects. Seems like a reasonable
hack, as long as commons-http-client was loaded by the
WebappClassLoader. ;)

- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkzxDgkACgkQ9CaO5/Lv0PAYagCgjN6tvR47NshlNwSojGO7LOp2
3eAAnisYOvsvoZBL8R34+azn+K3ZTpoi
=3DRAzC
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


DISCLAIMER:
Orange Lake Resorts does not accept legal responsibility for the =
contents of this message. Orange Lake Resorts reserves the right to =
monitor the transmission of this message and to take corrective action =
against any misuse or abuse of its e-mail system or other components of =
its network. The information contained in this e-mail is confidential =
and may be legally privileged.  It is intended solely for the addressee. =
If you are not the intended recipient, any disclosure, copying, =
distribution, or any action or act of forbearance taken in reliance on =
it, is prohibited and may be unlawful. Any views expressed in this =
e-mail are those of the individual sender, except where the sender has =
been duly authorized to specifically state the content of the e-mail on =
behalf of Orange Lake Resorts.  The recipient should check this e-mail =
and any attachments for the presence of viruses. Orange Lake Resorts =
accepts no liability for any damage caused by any viruses transmitted by =
this e-mail.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org