lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Fuad Efendi (JIRA)" <>
Subject [jira] Commented: (SOLR-2233) DataImportHandler - JdbcDataSource is not thread safe
Date Thu, 11 Nov 2010 20:28:15 GMT


Fuad Efendi commented on SOLR-2233:

This is exception I was talking about, threads="16", 12 sub-entities, with existing trunk
version, note *The connection is closed*

The connection is closed.
        at org.apache.solr.handler.dataimport.DataImportHandlerException.wrapAndThrow(
        at org.apache.solr.handler.dataimport.JdbcDataSource$ResultSetIterator.hasnext(
        at org.apache.solr.handler.dataimport.JdbcDataSource$ResultSetIterator.access$600(
        at org.apache.solr.handler.dataimport.JdbcDataSource$ResultSetIterator$1.hasNext(
        at org.apache.solr.handler.dataimport.EntityProcessorBase.getNext(
        at org.apache.solr.handler.dataimport.SqlEntityProcessor.nextRow(
        at org.apache.solr.handler.dataimport.ThreadedEntityProcessorWrapper.nextRow(
        at org.apache.solr.handler.dataimport.DocBuilder$EntityRunner.runAThread(
        at org.apache.solr.handler.dataimport.DocBuilder$
        at org.apache.solr.handler.dataimport.DocBuilder$EntityRunner.runAThread(
        at org.apache.solr.handler.dataimport.DocBuilder$EntityRunner.access$000(
        at org.apache.solr.handler.dataimport.DocBuilder$EntityRunner$
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
        at java.util.concurrent.ThreadPoolExecutor$
Caused by: The connection is closed.
        at org.apache.solr.handler.dataimport.JdbcDataSource$ResultSetIterator.hasnext(
        ... 13 more

> DataImportHandler - JdbcDataSource is not thread safe
> -----------------------------------------------------
>                 Key: SOLR-2233
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: 1.5
>            Reporter: Fuad Efendi
>         Attachments: FE-patch.txt, SOLR-2233-JdbcDataSource.patch
> Whenever Thread A spends more than 10 seconds on a Connection (by retrieving records
in a batch), Thread B will close connection.
> Related exceptions happen when we use "threads=" attribute for entity; usually exception
stack contains message "connection already closed"
> It shouldn't happen with some JNDI data source, where Connection.close() simply returns
Connection to a pool of available connections, but we might get different errors.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

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

View raw message