Fix IndexOutOfBoundsException
in Strand Dump Tool and refactor logic
#43707
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose
Approach
Fix
When parsing the generated Java thread report, there can be cases where a virtual thread is present but its relevance to Ballerina cannot be established. Then, details about that thread won't be added to the list of Ballerina Strand details. Therefore, it is wrong to assume that the
balStand
array will have a 1:1 mapping for eachid
generated during the parsing resulting in anIndexOutOfBoundsException
. This can be mitigated but using aMap
with theid
as the key instead of using anArrayList
.Refactoring
Broaden the scope of identifiers so that important ballerina related strands aren't missed.
Check List