[
https://issues.apache.org/jira/browse/SOLR-14302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17067891#comment-17067891
]
ASF subversion and git services commented on SOLR-14302:
--------------------------------------------------------
Commit f760d3cf52c0621dcf8942926410f29f2a8d5c11 in lucene-solr's branch
refs/heads/branch_8x from Chris M. Hostetter
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=f760d3c ]
SOLR-14302: Ensure Solr always includes the stacktrace for exceptions by using
'-OmitStackTraceInFastThrow'
(cherry picked from commit 255132fc1c6d4639db3becb6b9501feb7dd6593c)
> 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
> 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
