new FAQ answer for connection close during non-blocking operations

mojolicious · Aug 27, 2016 · a78557c · a78557c
1 parent 0391bb3
commit a78557c
Showing 1 changed file with 10 additions and 0 deletions.
diff --git a/lib/Mojolicious/Guides/FAQ.pod b/lib/Mojolicious/Guides/FAQ.pod
@@ -259,6 +259,16 @@ will force the affected worker to be restarted after a timeout. This timeout
 defaults to C<20> seconds and can be extended with the attribute
 L<Mojo::Server::Prefork/"heartbeat_timeout"> if your application requires it.
 
+=head2 What does "Connection already closed" mean?
+
+This error message usually appears after waiting for the results of a
+non-blocking operation for longer periods of time, because the underlying
+connection has been closed in the meantime and the value of the attribute
+L<Mojolicious::Controller/"tx"> is no longer available. While there might not be
+a way to prevent the connection from getting closed, you can also avoid this
+error message by keeping a reference to the transaction object that is not
+weakened.
+
 =head1 MORE
 
 You can continue with L<Mojolicious::Guides> now or take a look at the