[
https://issues.apache.org/jira/browse/SOLR-3379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sami Siren resolved SOLR-3379.
------------------------------
Resolution: Fixed
I missed this issue completely earlier, sorry about that. I merged my earlier
commit from 4.x (1332160) so this is now fixed also in 3.6.1 (1351779).
Thanks David for reporting the problem and also providing the fix!
> Make logging of threadpool configuration report correct values
> --------------------------------------------------------------
>
> Key: SOLR-3379
> URL: https://issues.apache.org/jira/browse/SOLR-3379
> Project: Solr
> Issue Type: Improvement
> Affects Versions: 3.6, 4.0
> Reporter: David M. Lyle
> Assignee: Sami Siren
> Priority: Minor
> Fix For: 4.0, 3.6.1
>
> Attachments: SOLR-3379-3x_branch.patch, SOLR-3379-trunk.patch
>
>
> SOLR-3221 allows configuration of the shard handler thread pool. When the
> thread pool configuration is changed the configuration changed is logged but
> the value reported is always the socket timeout.
> This patch will report the value of the configuration item changed.
--
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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
