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

Fix for IllegalStateException on Thread Rejection with Response Caching #120

Merged
merged 1 commit into from
Feb 28, 2013
Merged

Fix for IllegalStateException on Thread Rejection with Response Caching #120

merged 1 commit into from
Feb 28, 2013

Conversation

benjchristensen
Copy link
Contributor

With the additional logging I was able to write a unit test that replicated the issue and fix it.
Rejected exceptions were not being handled correctly.

#113

With the additional logging I was able to write a unit test that replicated the issue and fix it.
Rejected exceptions were not being handled correctly.

#113
benjchristensen added a commit that referenced this pull request Feb 28, 2013
Fix for IllegalStateException on Thread Rejection with Response Caching
@benjchristensen benjchristensen merged commit 3f6987d into Netflix:master Feb 28, 2013
@cloudbees-pull-request-builder

Hystrix-pull-requests #1 FAILURE
Looks like there's a problem with this pull request

@benjchristensen
Copy link
Contributor Author

Ignoring CloudBees for now ... some non-deterministic unit tests need to be fixed and CloudBees instances quite reliably cause issues whereas the Netflix Jenkins build never (or rarely) does.

@benjchristensen
Copy link
Contributor Author

I let 2 instances run as production canaries for 24+ hours with higher than normal load (higher RPS driven by weighted-load-balancing being increased for these boxes) and didn't see any "Response Not Available" logs on either machine.

I am going to proceed with releasing this code.

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

Successfully merging this pull request may close these issues.

2 participants