Fwd: Structured Concurrency - Stacktrace in tree hierarchical structure

[Alan Bateman]

On 27/11/2024 18:14, Abdul Muneer K wrote:
> Hi,
> I prepared a StructuredTaskScope in a tree hierarchical structure as 
> below:
>                         TaskA
>                            __|__
>                  TaskB             Tasks
>                ___|__.               __|___
>            TaskD.  TaskE.   TaskF .     TaskG
>
> [Not sure it will show as a tree while sending email because of 
> formatting, basically it's a three level full tree.]
>
> I captured the stack trace using the below command while running this 
> sample code with some delays on each task, so that I can capture 
> thread dumps with all of these tasks in the running state.
> I ran below command to get thread dumps in json format:
> jcmd <pid> Thread.dump_to_file -format=json <file>
>
> I got the thread dump, my expectation was, threads will follow the 
> same tree structure in thread dump also. We can track it based on the 
> fields "owner" and "parent". But, it will be difficult to follow based 
> on these fields if we have too many threads.
> Is it designed like that because of any limitations? Or am I missing an
>
I don't think I understand your question. Are you asking about the 
traversal order used when streaming it to a file or are you asking if 
the owner and parent keys are the right way to reconstitute the tree?

-Alan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/loom-dev/attachments/20241127/6f504583/attachment-0001.htm>