fix misconfiguration in application.conf timeouts #181
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
👍 merging |
rushtong
added a commit
that referenced
this pull request
Jan 6, 2016
fix misconfiguration in application.conf timeouts
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
this does not fully fix the issue for the end user.
There was a simple misconfiguration in our application.conf - previously, I was trying to set spray.can.spray.can.client timeouts, not spray.can.client.
After this change is in place, the bug in question now gets 504 timeouts after 60 seconds. This is probably a timeout from the Apache proxy and needs to be fixed by devops - but this PR is a prerequisite.