You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-dev@lucene.apache.org by "Michael Henson (JIRA)" <ji...@apache.org> on 2010/02/05 03:16:27 UTC

[jira] Updated: (SOLR-1757) DIH multithreading sometimes throws NPE

     [ https://issues.apache.org/jira/browse/SOLR-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Henson updated SOLR-1757:
---------------------------------

    Attachment: solr-1352-threads-bt.txt

This is the backtrace I get with this NPE. The backtrace is always the same, though I haven't confirmed whether or not it happens with the same data or after the same number of rows have been processed. The redacted part of the backtrace looked normal - no missing fields, no empty values.

> 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
>         Attachments: solr-1352-threads-bt.txt
>
>
> 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.