F
frank.meulblok
Guest
Sessions ("logical threads") can and will hop to different process threads in the same agent ("physical threads") . If you're using shared libraries/dlls that can be a trigger for threading issues. That's the one case I can think of where you would be interested in knowing the actual threadIDs. Especially if you have debug access to the 3rd-party library the actual threadID is something you should be able to recognise on the library's side to see the whole roundtrip of the call. What I assume to be the sequence number of the thread within the thread pool the PASOE agent maintains isn't going to be too helpful in that case.
Continue reading...
Continue reading...