[ https://issues.apache.org/jira/browse/SOLR-11880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16335473#comment-16335473 ]
Shalin Shekhar Mangar commented on SOLR-11880: ---------------------------------------------- I don't think that is possible. If we want the caller's stack trace then we either call fillInStackTrace at the point of the call or we use a cached copy from the right place. If this is indeed a bottleneck (and I am not sure that it is) then we can either eliminate the submitter stack trace with a flag or do something ugly/clever like having the caller of execute method pass down a static exception object > Avoid creating new exceptions for every request made via > MDCAwareThreadPoolExecutor > ----------------------------------------------------------------------------------- > > Key: SOLR-11880 > URL: https://issues.apache.org/jira/browse/SOLR-11880 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Reporter: Varun Thacker > Priority: Minor > > MDCAwareThreadPoolExecutor has this line in it's{{{execute}} method > > {code:java} > final Exception submitterStackTrace = new Exception("Submitter stack > trace");{code} > This means that every call via the a thread pool will create this exception, > and only when it sees an error will it be used. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org