[
https://issues.apache.org/jira/browse/SOLR-12611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16565890#comment-16565890
]
Shawn Heisey commented on SOLR-12611:
-------------------------------------
Attached patch against branch_7x that creates a thread on startup. The thread
is given a name that includes full version information. The thread is set up
to wait on synchronization, which I figure is probably the most efficient way
for a thread to do absolutely nothing. If there's a better option, let me
know. At Solr shutdown, the thread is sent an interrupt, which breaks it out
of its synchronization wait and allows the thread to end.
> Add version information to thread dump
> --------------------------------------
>
> Key: SOLR-12611
> URL: https://issues.apache.org/jira/browse/SOLR-12611
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Affects Versions: 7.4
> Reporter: Shawn Heisey
> Priority: Trivial
> Attachments: SOLR-12611.patch
>
>
> Thread dumps contain stacktrace info. Without knowing the Solr version, it
> can be difficult to compare stacktraces to source code.
> If exact version information is available in the thread dump, it will be
> possible to look at source code to understand stacktrace information. If
> *full* version information is present, then it would even be possible to
> learn whether the user is running an official binary build or if they have
> built Solr themselves.
--
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
