[ 
https://issues.apache.org/jira/browse/SOLR-17439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17881222#comment-17881222
 ] 

ASF subversion and git services commented on SOLR-17439:
--------------------------------------------------------

Commit 97d7d42d49b57a0b4156e48a50de83f683c1eca6 in solr's branch 
refs/heads/branch_9x from rmueller83
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=97d7d42d49b ]

SOLR-17439 Fix missing documentation for finding out non-standard PID (#2705)

(cherry picked from commit c57c6d96067c8e6057c95539de59b9c5e83a3e0b)


> jattach does not work with Solr in Docker
> -----------------------------------------
>
>                 Key: SOLR-17439
>                 URL: https://issues.apache.org/jira/browse/SOLR-17439
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: Docker
>    Affects Versions: 9.6.1
>            Reporter: Roland Müller
>            Assignee: Jan Høydahl
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> I am running the solr:9.6.1 Docker image and want to create a heap dump.
> According to the documentation this should be possible using jattach: 
> [https://solr.apache.org/guide/solr/latest/deployment-guide/solr-in-docker.html#debugging-with-jattach]
> If I open a shell in the container and enter the sample command from the 
> documentation, this is what I get:
> {noformat}
> $ jattach 10 threaddump
> Process 10 not found{noformat}
> using the default PID 1, there is a different error:
> {noformat}
> $ jattach 1 threaddump
> Could not start attach mechanism: No such file or directory {noformat}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org

Reply via email to