You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Steve Wolfe (Closed) (JIRA)" <ji...@apache.org> on 2011/12/21 13:31:30 UTC

[jira] [Closed] (SOLR-2980) DataImportHandler becomes unresponsive with Microsoft JDBC driver

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

Steve Wolfe closed SOLR-2980.
-----------------------------

    Resolution: Not A Problem

Determined that the issue is not Solr-specific, but rather it occurs between affected versions/builds of the JRE and the MS SQL JDBC driver.  See comment for details.
                
> DataImportHandler becomes unresponsive with Microsoft JDBC driver
> -----------------------------------------------------------------
>
>                 Key: SOLR-2980
>                 URL: https://issues.apache.org/jira/browse/SOLR-2980
>             Project: Solr
>          Issue Type: Bug
>          Components: contrib - DataImportHandler
>    Affects Versions: 3.4, 3.5
>         Environment: Java JRE 1.6.0_20, JRE 1.6.0_29, CentOS (kernel 2.6.18-274.3.1.e15), Microsoft SQL Server JDBC Driver 3.0
>            Reporter: Steve Wolfe
>              Labels: dataimport, jdbc, solr, sql, sqlserver
>
> A solr core has been configured to use the DataImportHandler to read a set of documents from a Microsoft SQL Server database, via the Microsoft JDBC driver.  A known-good configuration for the data import handler is used, and a "reload-config" followed by "full-import" command are issued to the DataImportHandler.
> The handler switches to a status of "A command is still running...", and shows 1 request has been made to the data source.  Subsequent status calls show the Time Elapsed growing, but the handler fails to perform any action--SQL Server confirms that a login event occurs, but no queries are issued.  Solr does not throw any exceptions, even after a very long duration.  The last message in Solr's output is "INFO: Creating a connection for entity {entity name} with URL: {entity datasource url}"
> Attempts to issue an Abort command to the DataImportHandler appear successful, but do no stop the operation.
> Running the solr instance with the "java -verbose" flag shows the following:
> *IMMEDIATELY UPON EXECUTING "FULL-IMPORT" COMMAND*
> [Loaded com.microsoft.sqlserver.jdbc.StreamPacket from file:/home/MYWEBGROCER/swolfe/downloads/apache-solr-3.5.0/example/lib/sqljdbc4.jar]
> [Loaded com.microsoft.sqlserver.jdbc.StreamLoginAck from file:/home/MYWEBGROCER/swolfe/downloads/apache-solr-3.5.0/example/lib/sqljdbc4.jar]
> [Loaded com.microsoft.sqlserver.jdbc.StreamDone from file:/home/MYWEBGROCER/swolfe/downloads/apache-solr-3.5.0/example/lib/sqljdbc4.jar]
> *APPROXIMATELY 40 SECONDS LATER*
> [Loaded java.io.InterruptedIOException from /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/rt.jar]
> [Loaded java.net.SocketTimeoutException from /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/rt.jar]
> [Loaded sun.net.ConnectionResetException from /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/rt.jar]
> An issue with identical symptoms has been reported on StackOverflow (the OP found that using a 3rd party JDBC driver appeared successful): http://stackoverflow.com/questions/8269038/solr-dataimporthandler-logs-into-sql-but-never-fetches-any-data

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org