[
https://issues.apache.org/jira/browse/SOLR-2233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12931225#action_12931225
]
Fuad Efendi commented on SOLR-2233:
-----------------------------------
And some real-life test, root entity contains 10 subentities, 16 threads
allocated,
*befor*
{code}
<str name="Time Elapsed">0:1:0.322</str>
<str name="Total Requests made to DataSource">7296</str>
<str name="Total Rows Fetched">8061</str>
<str name="Total Documents Processed">729</str>
{code}
*after*
{code}
<str name="Time Elapsed">0:1:1.184</str>
<str name="Total Requests made to DataSource">0</str>
<str name="Total Rows Fetched">29247</str>
<str name="Total Documents Processed">2639</str>
{code}
Look at it, it seems we don't unnecessarily close connection!
*Total Requests made to DataSource: 0*
> DataImportHandler - JdbcDataSource is not thread safe
> -----------------------------------------------------
>
> Key: SOLR-2233
> URL: https://issues.apache.org/jira/browse/SOLR-2233
> 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: [email protected]
For additional commands, e-mail: [email protected]
