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 Fri, 12 Nov 2010 13:53:14 GMT


Fuad Efendi commented on SOLR-2233:

The only remaining problem is what to do if Database Server closed/dropped connection or something
like that (for instance, due to timeout settings on a database, or due to heavy load, or network
problem). The more time required to index data, the more frequent problems.

Even connection pool (accessed via JNDI) won't help because existing (and new) code tries
to keep the same connection for a long time, without any logic to check that connection is
still alive. What to do if we are in the middle of RecordSet and database dropped connection?


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