Share

Heritrix: Internet Archive Web Crawler

Tracker: Bugs

5 fatal runtimeexceptions in frontier give no info in web UI - ID: 1000929
Last Update: Comment added ( karl-ia )

The recent CCE problem was only evident in the stdout
log -- because it involved an uncaught runtime
exception (CCE) which triggered default behavior (dump
stack, end execution of that thread).

These should be caught and noted in the UI somehow.

(Additionally, looking at the Thread report gives no
indication that the threads are completely dead, rather
than just hung, because the state consulted for that
report is all still around. We probably need to add an
isAlive() check to that report -- and the general
thread-status assessment.)


Gordon Mohr ( gojomo ) - 2004-07-30 20:38

5

Closed

Duplicate

Nobody/Anonymous

None

None

Public


Comments ( 2 )

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


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


Date: 2004-10-14 18:36
Sender: stack-sfProject Admin

Logged In: YES
user_id=924942

This issue was closed as a duplicate of '[ 965622 ] Serious
error during crawling did not produce an alert'
https://sourceforge.net/tracker/index.php?func=detail&aid=965622&group_id=73833&atid=539099


Attached File

No Files Currently Attached

Changes ( 3 )

Field Old Value Date By
status_id Open 2004-10-14 18:35 stack-sf
resolution_id None 2004-10-14 18:35 stack-sf
close_date - 2004-10-14 18:35 stack-sf