[ https://issues.apache.org/jira/browse/SOLR-15010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17238332#comment-17238332 ]
David Smiley commented on SOLR-15010: ------------------------------------- The reason this is happening is very very likely because you are running in Solr's docker image, which only runs with a JRE (no jstack etc. utilities). [~janhoy] made this change and he supplied the small "jattach" utility as a substitute. I think instead of making this warning go away, let's make add the equivalent functionality via jattach? The equivalent syntax is "jattach <pid> threaddump". We can't do this via an alias but maybe a bash function? > Missing jstack warning is alarming, when using bin/solr as client interface > to solr > ----------------------------------------------------------------------------------- > > Key: SOLR-15010 > URL: https://issues.apache.org/jira/browse/SOLR-15010 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) > Affects Versions: 8.7 > Reporter: David Eric Pugh > Priority: Minor > > In SOLR-14442 we added a warning if jstack wasn't found. I notice that I > use the bin/solr command a lot as a client, so bin solr zk or bin solr > healthcheck. > For example: > {{docker exec solr1 solr zk cp /security.json zk:security.json -z zoo1:2181}} > All of these emit the message: > The currently defined JAVA_HOME (/usr/local/openjdk-11) refers to a location > where java was found but jstack was not found. Continuing. > This is somewhat alarming, and then becomes annoying. Thoughts on maybe > only conducting this check if you are running {{bin/solr start}} or one of > the other commands that is actually starting Solr as a process? -- 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