[
https://issues.apache.org/jira/browse/LUCENE-4595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13525891#comment-13525891
]
Robert Muir commented on LUCENE-4595:
-------------------------------------
+1 to commit this fix, I ran with patch:
{noformat}
[junit4:junit4] JVM J0: 1.02 .. 362.37 = 361.35s
[junit4:junit4] JVM J1: 1.02 .. 362.21 = 361.20s
[junit4:junit4] JVM J2: 1.02 .. 362.41 = 361.39s
[junit4:junit4] JVM J3: 1.02 .. 362.33 = 361.31s
[junit4:junit4] Execution time total: 6 minutes 2 seconds
[junit4:junit4] Tests summary: 10000 suites, 10000 tests
[echo] 5 slowest tests:
[junit4:tophints] 0.01s |
org.apache.lucene.benchmark.byTask.feeds.EnwikiContentSourceTest
BUILD SUCCESSFUL
Total time: 6 minutes 11 seconds
{noformat}
Thanks Doron.
> EnwikiContentSource thread safety problem (NPE) in 'forever' mode
> -----------------------------------------------------------------
>
> Key: LUCENE-4595
> URL: https://issues.apache.org/jira/browse/LUCENE-4595
> Project: Lucene - Core
> Issue Type: Bug
> Components: modules/benchmark
> Reporter: Doron Cohen
> Assignee: Doron Cohen
> Priority: Minor
> Attachments: LUCENE-4595.patch
>
>
> If close() is invoked around when an additional input stream reader is
> recreated for the 'forever' behavior, an uncaught NPE might occur.
> This bug was probably always there, just exposed now with the
> EnwikioContentSourceTest added in LUCENE-4588.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
