[
https://issues.apache.org/jira/browse/SOLR-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Henson updated SOLR-1757:
---------------------------------
Attachment: solr-1757-abort-threaddump.zip
This is the ../admin/threaddjump.jsp page for the core configured with
threads="3", running a full-import, after having sent it the abort command.
> DIH multithreading sometimes throws NPE
> ---------------------------------------
>
> Key: SOLR-1757
> URL: https://issues.apache.org/jira/browse/SOLR-1757
> Project: Solr
> Issue Type: Bug
> Components: contrib - DataImportHandler
> Affects Versions: 1.4
> Environment: tomcat 6.0.x, jdk 1.6.x on windows xp 32bit
> Reporter: Michael Henson
> Assignee: Noble Paul
> Attachments: solr-1352-threads-bt.txt,
> solr-1757-abort-threaddump.zip, SOLR-1757.patch
>
>
> When the "threads" attribute is set on a root entity in the DIH's
> data-config.xml, the multithreading code sometimes throws a
> NullPointerException after the full-index command is given.
> I haven't yet been able to figure out exactly which reference holds the null
> or why, but it does happen consistently with the same backtrace.
> My configuration is:
> 1. Multi-core Solr under tomcat
> 2. Using JdbcDataSource and the default SqlEntityProcessor
> To reproduce:
> 1. Add the attribute threads="2" to the root entity declaration in
> data-config.xml
> 2. Send the full-import command either directly to
> .../core/dataimport?command=full-import or through the /admin/dataimport.jsp
> control panel.
> 3. Wait for the NPE to show up in the logs/console
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
