This page describes all problems, tasks and solution approaches regarding tracing of method invocations that can span over multiple threads.
Main topics
How to access information about the current method?
- How to handle asynchronous methods, that are still running after its parent are already terminated?
- How to tell the called method who is its caller or parent?
- How to find out the three points of interest in threads?
- How to tell, what thread created the current thread, what thread called it and what thread is executing it?
- How to handle thread pools?
- Is there a universal solution for every thread pool implementation?
Current solution (state)
(Previous solution approaches regarding this topic were already discussed in the master thesis.)
TODO: Validate if asynchronous methods are currently supported / traced by the sequence sensor. Possibly there were improvements in the meantime.
New approaches / solution
Coming soon...
Questions / Possible Problems
- An asynchronous method invocation has no fixed start and end point. Is possible, that a asynchronous methods is still running after its caller is already finished.
- How can i modify the start() method on Threads, to get the information about the Thread creator, caller and executor?