No, reverting back to Tomcat 5 would remove the error message, but not eliminate the problem. I have some ideas where this comes from. Can you please open a JIRA issue for this?
Andreas On Wed, Nov 24, 2010 at 22:02, Emerson, Christopher <cemer...@orangelake.com> wrote: > Is this something that I need to consider reverting back to Tomcat 5? > > > > ________________________________ > > From: Emerson, Christopher > Sent: Wednesday, November 24, 2010 10:04 AM > To: 'java-user@axis.apache.org' > Subject: Please help MultiThreadedHttpConnectionManager cleanup leak > > > > Ever since we've upgraded to Tomcat 6 4 weeks ago, I've been fighting > > the following error on shutdown ... > > > > Nov 23, 2010 4:42:18 PM org.apache.catalina.loader.WebappClassLoader > clearReferencesThreads > > 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. > > > > I have now upgraded to Axis2 1.5.1 on Tomcat 6.0.29. I only get this error > when an Axis2 web service is called from an ADB client from one of my APIs. > This happens on both windows and linux. Please point me in the right > direction. I’ve completely stripped down my config to try and narrow down > the problem. > > > > I’ve tried with and without my own MultiThreadedHttpConnectionManager. > > I’ve tried with and without my own ConfigurationContext. > > > > The latest test was with just creating a stub and leave Axis2 handle > everything else. > > > > employeeStub = new EmployeeServiceSMARTStub(params.getLocalServiceUrl() + > "EmployeeServiceSMART.EmployeeServiceSMARTHttpSoap12Endpoint/"); > > > > employeeStub._getServiceClient().getOptions().setTimeOutInMilliSeconds(2 * > 60 * 1000); > > employeeStub._getServiceClient().getOptions().setProperty(HTTPConstants.SO_TIMEOUT, > > 30000); > > employeeStub._getServiceClient().getOptions().setProperty(HTTPConstants.CONNECTION_TIMEOUT, > > 30000); > > employeeStub._getServiceClient().getOptions().setProperty(HTTPConstants.CHUNKED, > > Boolean.TRUE); > > employeeStub._getServiceClient().getOptions().setCallTransportCleanup(true); > > employeeStub._getServiceClient().getOptions().setProperty(HTTPConstants.HTTP_PROTOCOL_VERSION, > > HTTPConstants.HEADER_PROTOCOL_10); > > > > I call the following in a finally block … > > employeeStub._getServiceClient().cleanupTransport(); > > employeeStub._getServiceClient().cleanup(); > > > > Thanx for any help on this!!! > > > > > > Chris | Emerson > > Team Lead & Architect > > Information Technology > > ----------------------------------------- > > The Family of Orange Lake Resorts > > 8505 W. Irlo Bronson Memorial Hwy. > > Kissimmee, FL 34747 > > Ext 1705 > > www.orangelake.com > > > > 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: java-user-unsubscr...@axis.apache.org For additional commands, e-mail: java-user-h...@axis.apache.org
