Quartz Scheduler issue

[Simon Doran]

Hi All,

  Great conference last week, guys!

  I'm just touching base on a problem that still hasn't gone away for many releases of XNAT now. Whenever I shut down Tomcat, I get entries like this in the logs.

 org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application [/XNAT_anonymised] 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.

   The result is that there are connections to postgres left open and Tomcat's java process is still running. On a "normal" system, I solve this with a simple ps aux | grep java; kill -9 ...

   However, when this happens on my high-availability system, killing said process appears to somehow screw up the "heartbeat" synchronisation processes and I can't restart tomcat. Does anyone know if there is a way of getting these processes to exit gracefully by themselves and leave Tomcat in a suitable state to restart.

  Thanks in advance.

Simon 

 

[Herrick, Rick]

Yes, that’s been an on-going issue. We haven’t really seen any negative effects ourselves from this, but at the very least it’s hideous. I’ve tried a few things in the past to try to resolve to no effect, but have a few more ideas to try out. I’ve created an issue for this problem: https://issues.xnat.org/browse/XNAT-4359. We’ll get this into 1.7 for sure.

 

-- 

Rick Herrick

Sr. Programmer/Analyst

Neuroinformatics Research Group

Washington University School of Medicine

(314) 740-5961

--
You received this message because you are subscribed to the Google Groups "xnat_discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to xnat_discussi...@googlegroups.com.
To post to this group, send email to xnat_di...@googlegroups.com.
Visit this group at https://groups.google.com/group/xnat_discussion.
For more options, visit https://groups.google.com/d/optout.

 

---

The materials in this message are private and may contain Protected Healthcare Information or other information of a sensitive nature. If you are not the intended recipient, be advised that any unauthorized use, disclosure, copying or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error, please immediately notify the sender via telephone or return mail.