Dangling thread is detected after gnizr is shutdown.

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Start gnizr
2. Add couple RSS bookmarks to be crawled
3. Login as 'gnizr'
4. Go to "Settings" -> Enable gnizr RSS robot
5. Wait for few minutes until the RSS robot waits up
6. Shutdown Tomcat (e.g. ./shutdown.sh)

What is the expected output? What do you see instead?

The tomcat server should shutdown properly and all threads that are related
to the running of gnizr should be terminated. 

However, if I follow the above 1-6 steps, sometimes a dangling Tomcat
thread appears after the server is shutdown. I suspect some internal thread
is not shutdown properly when the gnizr Spring objects are terminated.

Original issue reported on code.google.com by harry.c...@gmail.com on 29 Feb 2008 at 4:36

[GoogleCodeExporter]

Original comment by harry.c...@gmail.com on 29 Feb 2008 at 4:37

• Added labels: Priority-Critical
• Removed labels: Priority-High

[GoogleCodeExporter]

Made some modifications to the implementation of CrawlRssFeed.java and
DefaultFeedCrawler.java in the gnizr-robot package. No longer forking new 
threads to
fetch RSS content from a URL. 

Original comment by harry.c...@gmail.com on 29 Feb 2008 at 4:59

• Changed state: Fixed