Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Uncaught exception in HttpResponse Can Cause Application Crash
See original GitHub issueHello,
The SendResponse method is writing into the OutputStream in a try ... finally block.
It so happens that sometimes there are network connection losses while writing the data.
OutputStream will raise an exception - and if it is not caught it will end up by crashing the whole process that launched RestServer.
For my initial tests, simply adding a catch in the try ... finally block solves the issue.
That specific request is obviously lost, but the process is not stopped any longer.
Probably adding some notification mechanism in the catch block would be even better.
Thank you for handling this rare case.
Best regards, SoftExpert
Issue Analytics
- State:
- Created 6 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Hi Scott,
Thank you again! I swear I am not picky 😉 , but I think there is still some place for an improvement see this GIST. WIth that one covered I think everything is good.
Best regards, SoftExpert
Hi,
is it correct that the fix to this issue is not yet part of the nugget which is still Version 4.1.1.0? Is there any plan to publish a new version with this issue fixed?
Best regards and keep up the good work findusl