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

Set MARKED_STALE_FLAG once timestamp update has been detected #11213

Merged
merged 1 commit into from
Nov 18, 2020

Conversation

hangshao0
Copy link
Contributor

When the SCC is open in readonly mode, MARKED_STALE_FLAG
should be set once timestamp update is detected for a class path
inside localValidate_CheckAndTimestampManually().

Closes #11110

Signed-off-by: Hang Shao hangshao@ca.ibm.com

When the SCC is open in readonly mode, MARKED_STALE_FLAG
should be set once timestamp update is detected for a class path
inside localValidate_CheckAndTimestampManually().

Closes eclipse-openj9#11110

Signed-off-by: Hang Shao <hangshao@ca.ibm.com>
@hangshao0
Copy link
Contributor Author

Manually tested. Having one JDK create the SCC, then remove the first JDK and install the second JDK at the same location.
Open the SCC in readOnly mode. The classes in the SCC are not returned to the second JDK.

@pshipton
Copy link
Member

jenkins test sanity,extended zlinux jdk8

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Unexpected JVM startup behavior when a release build java uses nightly build SCC
2 participants