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

Further AMQ handling improvement #62

Closed
tkohegyi opened this issue Sep 23, 2015 · 2 comments
Closed

Further AMQ handling improvement #62

tkohegyi opened this issue Sep 23, 2015 · 2 comments
Assignees

Comments

@tkohegyi
Copy link
Contributor

Despite the already existing self-defense mechanism that monitors the Active MQ queue sizes, it may still happen that a few message cause OOM close situation in case the messages are huge.

In order to keep Wilma stability even in such exceptional cases, we need to monitor the percentage of the used memory, and act in case AMQ use an unsafe level of memory, and restart the AMQ, to reset its memory usage. What we loose: some (huge) messages won't be logged - what we win: Wilma will survive killer size messages too.

Of course this mechanism will be activated only when the allocated/available memory size is not enough to handle the amount and size of the messages (so other solution is to increase the allocated memory).

@tkohegyi tkohegyi self-assigned this Sep 23, 2015
tkohegyi added a commit that referenced this issue Sep 23, 2015
tkohegyi added a commit that referenced this issue Sep 24, 2015
@tkohegyi
Copy link
Contributor Author

Under test, if solution works well, a new release will be published.

@tkohegyi
Copy link
Contributor Author

tkohegyi commented Oct 9, 2015

ok, closing, will be released in V1.2.83

@tkohegyi tkohegyi closed this as completed Oct 9, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant