Getting stack trace between fibers
Alan.Bateman at oracle.com
Wed Oct 31 14:16:38 UTC 2018
On 31/10/2018 13:51, Fabio Tudone wrote:
> I think the same as for threads, for example monitoring and visibility
> in general (e.g. in Quasar where "getStackTrace" is provided by the
> common "Strand" API).
The original motivation for Thread.getAllStackTraces/getStackTrace was
to provide an API to do something equivalent to the SIGQUIT handler. I
wouldn't expect a dump of hundreds of thousands of fibers to be
interesting but a subset of "important fibers" might be. So I think we
need to dig into it a bit more, maybe in conjunction with the monitoring
& management in java.lang.management to see what makes sense to expose.
More information about the loom-dev