Closed mlmarius closed 7 years ago
issue was caused by tornado's kqueue implementation
I'm glad you have solved.
Cheers
On 21 November 2017 at 03:04, mlmarius notifications@github.com wrote:
issue was caused by tornado's kqueue implementation
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/FSX/momoko/issues/157#issuecomment-345741346, or mute the thread https://github.com/notifications/unsubscribe-auth/AADjWTVZC-vRUbYDQrGT2o5Zyd_JphBmks5s4aMKgaJpZM4Qjf-n .
-- Zaar
I am trying out momoko for a project using python 3.6, tornado 4.5.2 and Momoko 2.2.4. In my initial tests I am testing the basic app ( https://github.com/FSX/momoko/blob/master/examples/gen_example.py ). First I built the example app and am trying to run it without the actual Postgresql server being reachable. Connection attempt fails but the app keeps continuing to run in a broken state. In order to test this the example app can be used with an unreachable Postgresql server.
Also, if during the lifetime of the app I take down the Docker container that runs Postgresql, the app also reaches this broken state on the first request, logs the error, keeps running but is unable to do anything.
Any ideas on how to manage this? Thanks!