On Monday, May 13, 2019 at 3:18:35 AM UTC-7, Krzysztof Jeleń wrote: [...]
> Current;y I'm not sure is this only Chrome issue, the problem is that > using DAL withput calling explicity DAL close method leave a lot of sockets > in wating state on server side. I was able to reduce its number to 30 (from > ~300) adding excplicity call to close method and removing DAL connection > for some requests which didn't need database (or I use my own db > abstraction layer with close mthod called explicity on postgreSQL > connection). From that point of view I'm pretty user that this issue is > kind of DAL error. > > >> >>> Considering how many different db.py files are out in the wild, including many production systems, and that we haven't seen much evidence of this before, I'd be surprised if it was purely a DAL error.. Have you tried wireshark or tcpdump on any of these to see what's happening in terms of handshakes, etc? /dps -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/web2py/56e76039-858b-4672-956c-5d296cdb952e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
