atom feed10 messages in net.sourceforge.lists.exist-openRe: [Exist-open] war file issue - han...
FromSent OnAttachments
Chris TomlinsonNov 13, 2012 2:28 am 
Dannes WesselsNov 13, 2012 3:07 am 
Chris TomlinsonNov 13, 2012 3:27 am 
Wolfgang MeierNov 13, 2012 11:42 am 
Chris TomlinsonNov 13, 2012 10:49 pm 
Joern TurnerNov 14, 2012 1:43 am 
Chris TomlinsonNov 14, 2012 7:34 am 
Dannes WesselsNov 14, 2012 7:40 am 
Joern TurnerNov 14, 2012 12:51 pm 
Chris TomlinsonNov 14, 2012 10:36 pm 
Subject:Re: [Exist-open] war file issue - hanging threads keep tomcat from terminating
From:Chris Tomlinson (chri@gmail.com)
Date:Nov 14, 2012 7:34:08 am
List:net.sourceforge.lists.exist-open

Hello Joern,

Great! I tried the patch and it works fine.

Thank you, Chris

On Nov 14, 2012, at 3:29 PM, Joern Turner <joer@gmail.com> wrote:

Hi,

the ehcache problem has been solved in betterFORM itself and that version has been updated in trunk but it seems that the necessary config in web.xml did not make it into the repo yet.

The following markup needs to be added to web.xml to stop the ehcache thread: <listener> <listener-class>de.betterform.agent.web.servlet.BfServletContextListener</listener-class> </listener>

We'll fix that in trunk asap.

On Wed, Nov 14, 2012 at 7:49 AM, Chris Tomlinson <chri@gmail.com> wrote:

Hello,

I've looked a bit more at the hanging threads and it appears that the QuartzScheduler threads in fact terminate. Even though the quartz scheduler reports that it is shutdown (BrokerPool line 1840), they are reported by tomcat as still running before tomcat actually shuts down ports and so forth:

Nov 14, 2012 12:09:50 PM org.apache.catalina.core.StandardServer await INFO: A valid shutdown command was received via the shutdown port. Stopping the Server instance. Nov 14, 2012 12:09:50 PM org.apache.coyote.AbstractProtocol pause INFO: Pausing ProtocolHandler ["http-bio-51173"] Nov 14, 2012 12:09:50 PM org.apache.coyote.AbstractProtocol pause INFO: Pausing ProtocolHandler ["ajp-bio-51176"] Nov 14, 2012 12:09:50 PM org.apache.catalina.core.StandardService stopInternal INFO: Stopping service Catalina Nov 14, 2012 12:09:50 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/exist] appears to have started a thread named [net.sf.ehcache.CacheManager@528f2588] but has failed to stop it. This is very likely to create a memory leak. Nov 14, 2012 12:09:50 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/exist] appears to have started a thread named [xfTestConfigOneElementInMemory.data] but has failed to stop it. This is very likely to create a memory leak. Nov 14, 2012 12:09:50 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/exist] appears to have started a thread named [DefaultQuartzScheduler_Worker-1] but has failed to stop it. This is very likely to create a memory leak. Nov 14, 2012 12:09:50 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/exist] appears to have started a thread named [DefaultQuartzScheduler_Worker-2] but has failed to stop it. This is very likely to create a memory leak. Nov 14, 2012 12:09:50 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/exist] appears to have started a thread named [DefaultQuartzScheduler_Worker-3] but has failed to stop it. This is very likely to create a memory leak. Nov 14, 2012 12:09:50 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/exist] appears to have started a thread named [DefaultQuartzScheduler_Worker-4] but has failed to stop it. This is very likely to create a memory leak. Nov 14, 2012 12:09:50 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [/exist] appears to have started a thread named [Thread-9] but has failed to stop it. This is very likely to create a memory leak. Nov 14, 2012 12:09:50 PM org.apache.coyote.AbstractProtocol stop INFO: Stopping ProtocolHandler ["http-bio-51173"] Nov 14, 2012 12:09:50 PM org.apache.coyote.AbstractProtocol stop INFO: Stopping ProtocolHandler ["ajp-bio-51176"] Nov 14, 2012 12:09:50 PM org.apache.coyote.AbstractProtocol destroy INFO: Destroying ProtocolHandler ["http-bio-51173"] Nov 14, 2012 12:09:50 PM org.apache.coyote.AbstractProtocol destroy INFO: Destroying ProtocolHandler ["ajp-bio-51176"]

jstack does not show the DefaultQuartzScheduler_Workers at this point. Only the betterform threads:

xfTestConfigOneElementInMemory.data

and

net.sf.ehcache.CacheManager

are still hanging.

I look forward to seeing the solution.

This is the remaining issue I know of that is specific to the war files.

Chris

On Nov 14, 2012, at 1:28 AM, Wolfgang Meier <wolf@exist-db.org> wrote:

We need to study how to stop these separate threads (ehcache and quartz).

The ehcache thread is used by betterform and I think Joern said he found a solution. The quartz thread should be stopped by eXist. At least it did so in the past.

------------------------------------------------------------------------------ Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov

------------------------------------------------------------------------------ Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov