[ 
https://issues.apache.org/jira/browse/SOLR-5342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shawn Heisey updated SOLR-5342:
-------------------------------

    Attachment: SOLR-5342.patch

New patch.  I went a little nuts and did lucene as well, so this issue (and the 
CHANGES mod) might need to move to lucene.

Questionable changes, due to verbosity of output:

org.apache.lucene.benchmark.byTask.feedsTrecContentSource#openNextFile
org.apache.lucene.demo.IndexFiles#main
various places in org.apache.solr.util.SimplePostTool

Places where I wasn't sure what change to make or whether any change was needed:

org.apache.lucene.index.TestDirectoryReaderReopen, line 322
org.apache.solr.cloud.OverSeerCollectionProcessor, line 1141
org.apache.solr.handler.TestReplicationHandler, lines 1330, 1370
org.apache.solr.servlet.ResponseUtils, line 47

Other stuff noticed along the way:

Dead code: org.apache.lucene.index.TestTransactions, line 197


> In some places, when a caught exception is re-thrown, the original exception 
> is not included
> --------------------------------------------------------------------------------------------
>
>                 Key: SOLR-5342
>                 URL: https://issues.apache.org/jira/browse/SOLR-5342
>             Project: Solr
>          Issue Type: Improvement
>    Affects Versions: 4.5
>            Reporter: Shawn Heisey
>            Assignee: Shawn Heisey
>            Priority: Minor
>             Fix For: 4.5.1, 4.6, 5.0
>
>         Attachments: SOLR-5342.patch, SOLR-5342.patch
>
>
> ShardHandlerFactory#newInstance catches exceptions and rethrows them.  It was 
> including the message from the caught exception, but not including the actual 
> exception.  This made it difficult to figure out the root cause for an SSL 
> initialization error.
> While fixing this, I discovered other places that are missing this as well.  
> Some of them I elected not to fix, either because it's catching IOException 
> (which normally provides good messages), or because it was in a location that 
> might get called frequently, which would greatly increase logging output.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to