True, but... Apache is not raising errors, web2py is. The error message is strange. At least we could have a nicer error if this can't be fixed. However in my example, both instances work until i try to log in. I can use the site without database i/o. Both instances work.
Now, why would web2py (1) raise an exception when working with database (2) because the apache (3) configuration is bad ? Sometimes the testing instance fails on login, sometimes it is production instance... I'd like to see more about Tamas's problem. Dana petak, 8. ožujka 2013. 15:05:01 UTC+1, korisnik Niphlod napisao je: > > wait a sec.... who binds to that socket is apache, not web2py :D > > On Friday, March 8, 2013 1:29:23 PM UTC+1, Tamas wrote: >> >> >> On Friday, March 8, 2013 11:57:39 AM UTC+1, Niphlod wrote: >>> >>> >>> >>> On Friday, March 8, 2013 11:06:00 AM UTC+1, Tamas wrote: >>>> >>>> Hello, >>>> >>>> I've been having this exact same problem for a long, long time. >>>> >>>> I would also be interested in a solution, but I doubt there will be >>>> one. I think it might be a design issue with Web2py. >>>> >>>> Tamas >>>> >>>> >>> I'm correct when I think that what you're asking is for two different >>> programs to bind to the same socket ? I don't think that's possibile with >>> whatever program, not only web2py. >>> >>> >> Not quite, we're using Apache WSGI, which in fact can run multiple >> instances of web2py on the same port, along with other python scripts as >> well. >> >> > -- --- 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.
