-
Notifications
You must be signed in to change notification settings - Fork 174
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
Kill Assault On a method call #322
Comments
Hi @vgaur The KillAppAssault is a RuntimeAssault. They need to be executed on your own or on a specific timeframe by specifing a cron expression like described in the docs to RuntimeAssaults. Currently its not possible to execute RuntimeAssaults when doing requests. So by either make a POST request to Can you please verify it if it works in your case? |
Thanks a lot @WtfJoke for your reply. Where it says To give you some background on what I was trying, I have some apache camel based demon processes and I wanted to test the app if the backend job fails at a particular method. |
Sorry for my late reply. That's a documentation issue. If I recall correctly the AppKiller Assault used to work once like that (before it was differentiated between Runtime/RequestAssaults). About your use case. Wont the Exception-Assault work in your case as well? |
@vgaur do you still have the requirement to kill the app on a request? If yes, could you elaborate on why an exception assault is not sufficient and you have to kill the entire application instead? |
I'll close this issue due to a lack of feedback. Feel free to open a new issue if necessary. 🙂 |
I am trying to add point cut on a method of service class and want the app to get killed when the method gets executed. Looked at the code of the interceptor and it seems it only works for RequestAssault and not on runtime assault.
I have provided detail on SO here
https://stackoverflow.com/questions/72824307/spring-boot-chaos-monkey-kill-assault
Expected Behavior
I was expecting to set the kill Assault point cut and when the code execution happen , the app should get killed.
Possible Solution
One possible way is to include Runtime Assault in interceptor.
The text was updated successfully, but these errors were encountered: