[
https://issues.apache.org/jira/browse/LUCENE-5572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17420059#comment-17420059
]
Dawid Weiss commented on LUCENE-5572:
-------------------------------------
bq. and it's not always us interrupting the threads
What is it that is interrupting the threads then? I'm sorry but it still does
seem like a design issue somewhere up the stack. The idiom you pointed at in
token info dictionary is fairly common in Java - I can't imagine your
application not coming across another place like this somewhere else if
interrupts come from unexpected places (with uninitialized classes still in the
queue).
> JapaneseTokenizer is sensitive to interrupts
> --------------------------------------------
>
> Key: LUCENE-5572
> URL: https://issues.apache.org/jira/browse/LUCENE-5572
> Project: Lucene - Core
> Issue Type: Improvement
> Components: modules/analysis
> Affects Versions: 3.6.2
> Reporter: Anthony Rasmussen
> Priority: Minor
>
> The constructor for JapaneseTokenizer gets the following singleton instances:
> TokenInfoDictionary, UnknownDictionary, and ConnectionCosts. I am finding
> that the associated getInstanceMethods are particularly sensitive to
> IOExceptions.
> Perhaps, in the static initializers of these 3 singletons, there could be
> some sort of retry effort before throwing a RunTimeException?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
