lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <>
Subject [jira] [Commented] (SOLR-4473) Reloading a core will not close (leak) associated DIH JDBC connection
Date Mon, 01 Apr 2013 20:11:15 GMT


Hoss Man commented on SOLR-4473:

I'm not certain, but i suspect what you are seeing is specific to the way derby's EmbeddedDiver
works.  As i understand it: you have to use a special jdbc connection string to tell derby
to shutdown the database, otherwise it will continue to run as long the JVM is up, even if
the Driver is properly closed (which should be happening when the DataSource is closed, when
the import is finished)...


> Reloading a core will not close (leak) associated DIH JDBC connection
> ---------------------------------------------------------------------
>                 Key: SOLR-4473
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>          Components: contrib - DataImportHandler
>    Affects Versions: 4.1
>            Reporter: Alexandre Rafalovitch
>             Fix For: 4.3
> I have DIH configured with Derby database. After I start Solr, I can run DIH import fine.
After I reload the core, DIH can no longer run with the following message (excerpts): 
> ...
> EVERE: Exception while processing: vac document : SolrInputDocument[]:org.apache.solr.handler.dataimport.DataImportHandlerException:
Unable to execute query: select * from ALERTS Processing Document # 1
> 	at org.apache.solr.handler.dataimport.DataImportHandlerException.wrapAndThrow(
> 	at org.apache.solr.handler.dataimport.JdbcDataSource$ResultSetIterator.<init>(
> 	at org.apache.solr.handler.dataimport.JdbcDataSource.getData(
> 	at org.apache.solr.handler.dataimport.JdbcDataSource.getData(
> 	at org.apache.solr.handler.dataimport.SqlEntityProcessor.initQuery(
> 	at org.apache.solr.handler.dataimport.SqlEntityProcessor.nextRow(
> 	at org.apache.solr.handler.dataimport.EntityProcessorWrapper.nextRow(
> 	at org.apache.solr.handler.dataimport.DocBuilder.buildDocument(
> Caused by: java.sql.SQLException: Another instance of Derby may have already booted the
database <PATH>.

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:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message