Yeah, you are correct there. How does this thing actually even
remotely begin to work on a predictable level?
On 6/4/07, Sami Siren (JIRA) <[EMAIL PROTECTED]> wrote:
[
https://issues.apache.org/jira/browse/NUTCH-496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12501266
]
Sami Siren commented on NUTCH-496:
----------------------------------
I believe the problem is even more severe. Now several threads share the
NgramProfile what is used to identify a piece of text, if parllel threads have
access to same object the reults are more or less random.
This could be fixed by changing the NGramProfile (what currently is a field
"suspect" in LanguageIdentifier) to be a thread local.
> ConcurrentModificationException can be thrown when getSorted() is called.
> -------------------------------------------------------------------------
>
> Key: NUTCH-496
> URL: https://issues.apache.org/jira/browse/NUTCH-496
> Project: Nutch
> Issue Type: Bug
> Components: fetcher
> Affects Versions: 0.9.0
> Environment: Nutch application, during fetch.
> Reporter: Briggs
> Attachments: language_analyzer_ngram.patch
>
>
> NGramProfile (within the org.apache.nutch.analysis.lang) package is not
thread-safe due to a ConcurrentModificationException that can occur if during
iteration of the resultant List from getSorted() and another call to getSorted()
is invoked from within another thread.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
--
"Conscious decisions by conscious minds are what make reality real"
