seems rather "famous". see https://github.com/psycopg/psycopg2/issues/263, https://devcenter.heroku.com/articles/postgres-logs-errors#pgerror-ssl-syscall-error-eof-detected, https://bitbucket.org/zzzeek/sqlalchemy/issue/3021/ssl-eof-not-detected-as-disconnect-in . I think (from a fast-read of the above) that the problem is that the connection is restarted in the middle of a transaction, and so the exception is raised. Not sure what web2py can do except maybe intercepting it return a more meaningful trace.
The fact is, even if the traceback is not "cristal clear", the transaction is lost because the connection misbehaved. <offtopic>Given that an exception is raised, I **think** the connection is recycled "properly", but we'd need a reproducible test-case to see if everything works fine. If web2py tries to reuse that same connection for another transaction, there it would lie a subtle bug (that **should need** to be fixed on the adapter side)...I doubt that the newly-opened cursor on that connection would be usable </offtopic> -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
