[
https://issues.apache.org/jira/browse/SOLR-2233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13177717#comment-13177717
]
Mikhail Khludnev commented on SOLR-2233:
----------------------------------------
David,
Please show your config excerpt, jstack and fullimport logs (DEBUG on
o.a.solr.dataimport), your connection pool config is quite appreciate too. I
can't say that I know which issue you are talking about.
I have patches for DIH multi-threadng and CachedSqlDatasource at trunk, 4.0.
SOLR-2933 SOLR-2947. Pls vote. Unfortunately it will be too much efforts to do
the same at 3.x. So, we need it committed and after that they can be ported
with SOLR-2382, or you will be able to try 4.0 DIH jars.
--
Mikhail
> DataImportHandler - JdbcDataSource is not thread safe
> -----------------------------------------------------
>
> Key: SOLR-2233
> URL: https://issues.apache.org/jira/browse/SOLR-2233
> Project: Solr
> Issue Type: Bug
> Components: contrib - DataImportHandler
> Affects Versions: 1.4, 1.4.1, 1.5, 3.1, 3.2
> Reporter: Fuad Efendi
> Attachments: SOLR-2233-001.patch, SOLR-2233-JdbcDataSource.patch,
> SOLR-2233.patch, SOLR-2233.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.
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: [email protected]
For additional commands, e-mail: [email protected]
