Share

Heritrix: Internet Archive Web Crawler

Tracker: Bugs

9 frontier report ConcurrentModificationException - ID: 1119644
Last Update: Comment added ( karl-ia )

I was clicking refresh for the following url
http://grape:8080/reports/frontier.jsp

and got the following error

jAn error occured

java.util.ConcurrentModificationException

java.util.ConcurrentModificationException
at
org.apache.commons.collections.bag.AbstractMapBag$BagIterator.next(Abstract
MapBag.java:205)
at
org.archive.crawler.frontier.BdbFrontier.appendQueueReports(BdbFrontier.jav
a:975)
at
org.archive.crawler.frontier.BdbFrontier.report(BdbFrontier.java:941)
at
org.archive.crawler.admin.CrawlJobHandler.getFrontierReport(CrawlJobHandler
.java:994)
at
org.archive.crawler.jspc.admin.reports.frontier_jsp._jspService(Unknown
Source)
at
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137)
at
javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:358)
at
org.mortbay.jetty.servlet.WebApplicationHandler$Chain.doFilter(WebApplicati
onHandler.java:342)
at
org.archive.crawler.admin.ui.RootFilter.doFilter(RootFilter.java:67)
at
org.mortbay.jetty.servlet.WebApplicationHandler$Chain.doFilter(WebApplicati
onHandler.java:334)
at
org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHand
ler.java:286)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:567)
at
org.mortbay.http.HttpContext.handle(HttpContext.java:1807)
at
org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContex
t.java:525)
at
org.mortbay.http.HttpContext.handle(HttpContext.java:1757)
at
org.mortbay.http.HttpServer.service(HttpServer.java:879)
at
org.mortbay.http.HttpConnection.service(HttpConnection.java:789)
at
org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:960)
at
org.mortbay.http.HttpConnection.handle(HttpConnection.java:806)
at
org.mortbay.http.SocketListener.handleConnection(SocketListener.java:218)
at
org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:300)
at
org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:511)


dave skinner ( frodobay ) - 2005-02-09 21:51

9

Closed

Fixed

Gordon Mohr

None

1.6.0

Public


Comments ( 3 )

Date: 2007-03-14 00:20
Sender: karl-ia


This issue is now discussed in the new JIRA tracker at
http://webteam.archive.org/jira/browse/HER-354 -- please add further
comments at that location.


Date: 2005-05-13 04:04
Sender: gojomoProject Admin

Logged In: YES
user_id=144912

The above stack specifically shows a problem occuring from
the inProcessQueues Bag. This may be the only collection
prone to this exception. So, changed report for that one
collection to work from a temporary copy that's made while
synchronized on the bag. May resolve problem completely, so
closing until recurs. Commit comment:

fix for [ 1119644 ] frontier report
ConcurrentModificationException
implementation of [ 1200205 ] add 'exhausted' queue count to
frontier report
* WorkQueueFrontier.java
- have report work from copy of inProcessBag -- will
eliminate specific ConcurrentModificationException reported
- add 'exhausted' queue count (created but now empty) to
one-line and full reports



Date: 2005-02-09 22:29
Sender: stack-sfProject Admin

Logged In: YES
user_id=924942

Thanks Dave. Its known issue (I just added note to release
notes).

Retry should get you the report eventually. We need to add
a synchronaization on iteration over threads but then thi s
report would be less 'live'.

We should fix this eventually but pegging it low priority
for now.


Attached File

No Files Currently Attached

Changes ( 8 )

Field Old Value Date By
artifact_group_id None 2005-09-23 18:27 gojomo
close_date - 2005-05-13 04:04 gojomo
status_id Open 2005-05-13 04:04 gojomo
resolution_id None 2005-05-13 04:04 gojomo
priority 4 2005-05-11 21:48 gojomo
assigned_to nobody 2005-05-11 21:48 gojomo
summary frontier ConcurrentModificationException 2005-02-09 22:29 stack-sf
priority 5 2005-02-09 22:29 stack-sf