Recently I upgraded to 2.32 from an older 1.99 version and have been running into an odd auth problem. I have 2 copies of an application hosted on a VM under one instance of web2py using Apache/WSGI. I can log into one of the apps however if I then try to login to the other copy I instead get a Ticket with the error "ProgrammingError: Cannot operate on a closed database". The database in this case is SQLite.
It does not matter which copy of the app I log into, it happens either direction. Once I start getting that error on one of the apps the error continues until I reset Apache. However the error only occurs with the Auth, other portions of the app that use database access work fine. The applications themselves are identical copies outside of some layout differences for looks and I use different DNS names for each. They do not share any auth through CAS etc. the auth_user tables are independent. I thought maybe it was session related since I was logging in from the same browser so I tried different session storage, cookies/db/files but that did not make a difference. The problem even happens if I log into one site from Firefox and then log into the second site with IE. The second site will then start giving this error. Does any have any ideas why logging into the second site would cause the database connection to close? I did not have this problem with 1.99 but I do not want to downgrade as I am starting to use newer features introduced. -- --- 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/groups/opt_out.
