You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Chris M. Hostetter (Jira)" <ji...@apache.org> on 2020/03/26 17:45:00 UTC
[jira] [Resolved] (SOLR-14302) Solr stops printing stacktraces in
log and output due to OmitStackTraceInFastThrow - regression of SOLR-7436
[ https://issues.apache.org/jira/browse/SOLR-14302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris M. Hostetter resolved SOLR-14302.
---------------------------------------
Fix Version/s: 8.6
master (9.0)
Resolution: Fixed
> Solr stops printing stacktraces in log and output due to OmitStackTraceInFastThrow - regression of SOLR-7436
> -------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-14302
> URL: https://issues.apache.org/jira/browse/SOLR-14302
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Affects Versions: 8.1
> Reporter: Chris M. Hostetter
> Assignee: Chris M. Hostetter
> Priority: Major
> Fix For: master (9.0), 8.6
>
> Attachments: SOLR-14302.patch
>
>
> I recently saw a person ask a question about an Exception in their logs that didn't have a stack trace even though it certainly seemed like it should.
> I was immediately suspicious that they may have tweaked their solr options to override the {{-XX:-OmitStackTraceInFastThrow}} that was added to bin/solr by SOLR-7436, but then i discovered it's gone now - removed in SOLR-13394 w/o any discussion/consideration (and possibly unintentionally w/o understanding it's purpose?)
> We should almost certainly restore this by default.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org