Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jep393 closeScope0 native does not interrupt accessor threads #13256

Closed
EricYangIBM opened this issue Jul 28, 2021 · 1 comment
Closed

Jep393 closeScope0 native does not interrupt accessor threads #13256

EricYangIBM opened this issue Jul 28, 2021 · 1 comment
Assignees
Labels
comp:vm project:panama Used to track Project Panama related work
Milestone

Comments

@EricYangIBM
Copy link
Contributor

RI behaviour expects that a thread that is accessing a memory segment that another thread is closing is interrupted with a ScopedMemoryAccess.Scope.ScopedAccessError. The TestHandshake test depends on this behaviour (see #13211).

@tajila tajila added comp:vm project:panama Used to track Project Panama related work labels Jul 28, 2021
@tajila tajila added this to the Release 0.28 (Java 17) milestone Jul 28, 2021
EricYangIBM added a commit to EricYangIBM/openj9 that referenced this issue Sep 17, 2021
`closeScope0` should interrupt scope accessor threads with a
`Scope.ScopedAccessError`.

Closes: eclipse-openj9#13256
Signed-off-by: Eric Yang <eric.yang@ibm.com>
@EricYangIBM
Copy link
Contributor Author

Closing as closeScope0 is no longer required to throw an exception in accessor threads (jdk19). See #15161 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
comp:vm project:panama Used to track Project Panama related work
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants