Debug hanging Clojure processes

Open
#391 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
clojure, java
Domain
documentation

Research direction

No documentation file or test is named. Find the relevant troubleshooting or debugging section, then use jcmd to identify a process and jstack to inspect its thread stacks, including the egrep example from the issue. Done means a newcomer can follow the steps to investigate a hanging Clojure process.

Written by the indexing model from the issue text.

Description

If you have a Clojure process that is hanging:

find the process id with jcmd
inspect the thread stacks with jstack. Takes a little bit of wading through the noise but it can tell you a lot of where your process is hanging.

also this stuff greps really well, especially if you have a common prefix for your own namespaces, like I can jstack $PID | egrep '(^"|lambdaisland)' and see each individual thread, and the stack frames that are in my own code

https://clojurians.slack.com/archives/CCY2V0U6A/p1626969791039800

Dominant language
Makefile
Stars
117
Forks
36
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from practicalli/clojure

All issues in practicalli/clojure

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.