This seems relevant: http://www.nabble.com/-jira--Created%3A-%28AXIS2-935%29-Connections-are- not-properly-released-causing-them-to-stick-in-the-%22CLOSE_WAIT%22-stat e-and-cause-%22Too-many-files-open%22-t2006592i20.html
-----Original Message----- From: Michael Lambert [mailto:[EMAIL PROTECTED] Sent: Thursday, September 27, 2007 5:12 PM To: [email protected] Subject: thousands of axis2 threads All, I have an application that heavily depends of web services... I am using custom axsi2.xml files located in differing directories that I use to instantiate a configurationcontext: configContext = ConfigurationContextFactory.createConfigurationContextFromFileSystem(nul l, AXIS2_CONFIG_PATH); sender = new ServiceClient(configContext, null); I am noticing that the connections arent cleaning up after themselves... after 3 hours of heavy traffic there were over 40k axis2 threads running. I have read that if you manually create configuationcontexts in the way that i am that you also have to manually clean up after them. To test this theory I stopped using the custom confs and the number of threads did indeed seem to stabalie somewhat. The problem is this: i NEED to use custom axis2.xml files for these connections. Can someone please confirm what needs to be done to cleanup after these service clients? Is it enought to simply call service.cleanup() in a finally block? Thanks... this is causing our dept a lot of greif right now. A prompt response would be wonderful! -- Democracy is two wolves and a lamb voting on what to have for lunch. Liberty is a well-armed lamb contesting the vote. -Ben Franklin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
