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.

Sign up for GitHub

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

Jump to bottom

[3.15] Set Java Heap limit as a Workaround for Keycloak container memory issues #2108

Merged
merged 1 commit into from
Oct 21, 2024
Merged

[3.15] Set Java Heap limit as a Workaround for Keycloak container memory issues #2108

merged 1 commit into from
Oct 21, 2024

Conversation

jcarranzan
Copy link
Contributor

Summary

It's a backport from #2067

Please select the relevant options.

  • Bug fix (non-breaking change which fixes an issue)
  • Dependency update
  • Refactoring
  • Backport
  • New scenario (non-breaking change which adds functionality)
  • This change requires a documentation update
  • This change requires execution against OCP (use run tests phrase in comment)

Checklist:

  • Methods and classes used in PR scenarios are meaningful
  • Commits are well encapsulated and follow the best practices

@jcarranzan jcarranzan requested a review from fedinskiy October 21, 2024 09:26
@jcarranzan jcarranzan marked this pull request as ready for review October 21, 2024 09:26
@fedinskiy fedinskiy changed the title Set Java Heap limit as a Workaround for Keycloak container memory issues [3.15] Set Java Heap limit as a Workaround for Keycloak container memory issues Oct 21, 2024
@jcarranzan jcarranzan merged commit a2a077b into quarkus-qe:3.15 Oct 21, 2024
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@fedinskiy fedinskiy fedinskiy approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@jcarranzan @fedinskiy