[
https://issues.apache.org/jira/browse/NUTCH-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285455#comment-13285455
]
Markus Jelsma commented on NUTCH-1356:
--------------------------------------
I came across an NPE when inspecting the logs. We use the patch on 1.5 and i
can't remember i've seen this error before. Is it related to this patch?
It is, unfortunately, not reproducible with the parserchecker. I should also
note that this fetcher is having a very tough job (all others finished a while
ago) so something is going on, perhaps eating up memory due to a leak somewhere
(Tika?).
{code}
2012-05-30 07:03:39,560 WARN org.apache.nutch.parse.ParseUtil: Error parsing
http://www.vvvroomshoopseboys.nl/e7-programma.html with
org.apache.nutch.parse.tika.TikaParser@2bd2e84e
java.util.concurrent.ExecutionException: java.lang.NullPointerException
at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:232)
at java.util.concurrent.FutureTask.get(FutureTask.java:91)
at org.apache.nutch.parse.ParseUtil.runParser(ParseUtil.java:162)
at org.apache.nutch.parse.ParseUtil.parse(ParseUtil.java:93)
{code}
> ParseUtil use ExecutorService instead of manually thread handling.
> ------------------------------------------------------------------
>
> Key: NUTCH-1356
> URL: https://issues.apache.org/jira/browse/NUTCH-1356
> Project: Nutch
> Issue Type: Improvement
> Reporter: Ferdy Galema
> Fix For: nutchgora, 1.6
>
> Attachments: NUTCH-1356-trunk-v2.patch, NUTCH-1356-trunk.patch,
> NUTCH-1356.patch
>
>
> Because ParseUtil manages it's own parser threads by creating a thread for
> every parse it sometimes happens that specific parsers are very expensive.
> For example, parsers that have threadlocal fields will initialize them for
> every item to be parsed.
> By simply introducing a caching ExecutorService the ParseUtil will be able to
> cache threads therefore parsing more efficient. See attached patch.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
