tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emerson, Christopher" <>
Subject RE: Please help ... [MultiThreadedHttpConnectionManager cleanup]
Date Sat, 27 Nov 2010 14:51:20 GMT
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

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 [] 
Sent: Saturday, November 27, 2010 8:56 AM
To: Tomcat Users List
Subject: Re: Please help ... [MultiThreadedHttpConnectionManager

Hash: SHA1


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
> This is very likely to create a memory leak.
> 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
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla -


To unsubscribe, e-mail:
For additional commands, e-mail:

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:
For additional commands, e-mail:

View raw message