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:14:27 UTC

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

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


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.


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

Posted by "Michael Henson (JIRA)" <ji...@apache.org>.
     [ 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.


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

Posted by "Noble Paul (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SOLR-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Noble Paul resolved SOLR-1757.
------------------------------

       Resolution: Fixed
    Fix Version/s: 1.5

comitted r907935

> 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
>             Fix For: 1.5
>
>         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.


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

Posted by "Michael Henson (JIRA)" <ji...@apache.org>.
     [ 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.


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

Posted by "Noble Paul (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/SOLR-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12831298#action_12831298 ] 

Noble Paul commented on SOLR-1757:
----------------------------------

I guess you have pasted the wrong stacktrace.

We can close this issue and open another for the persistent threads after 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.


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

Posted by "Michael Henson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/SOLR-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12830395#action_12830395 ] 

Michael Henson commented on SOLR-1757:
--------------------------------------

The patch works to get it running. Now the issue is that the process doesn't stop after an "abort" command is given.

> 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.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.


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

Posted by "Noble Paul (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SOLR-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Noble Paul reassigned SOLR-1757:
--------------------------------

    Assignee: Noble Paul

> 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
>
>
> 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.


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

Posted by "Noble Paul (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SOLR-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Noble Paul updated SOLR-1757:
-----------------------------

    Attachment: SOLR-1757.patch

> 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.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.


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

Posted by "Noble Paul (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/SOLR-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12830450#action_12830450 ] 

Noble Paul commented on SOLR-1757:
----------------------------------

thanks Micheal. I'll commit this soon

could you help me w/ the thread dumps after the abort. 

> 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.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.