Re: ID of thread that waken up by notify()
Yao Qi wrote:
I think Bytecode instrumentation could do the same thing as your
mentioned above, and currently, we are using ASM to do instrumentation.
Yes. But I'm afraid that it won't work in your situation.
To wrap the original native methods of Object, there is required support
for a native methods prefix change, which is a new instrumentation 1.6
feature (setNativeMethodPrefix()).
I think the only problem in on notify(), because one thread is picked up
from "wait set", and is resumed to run, but we could not know which thread is
picked up and resumed to run.
For me, it seams to be easiest part of your problem. Patricia already
suggested a solution based on queues. You may also consider using a Map
of Sets of Threads keyed by objects for which wait() has been called.
Or develop some other method...
I still thinking how to solve this problem by means of instrumentation.
I think it's impossible because of the following requirement:
our
target jdk is jdk 5.
With that, probably the only way to solve it, is to use JPDA (already
pointed out by Lew).
piotr