On Saturday, April 28, 2018 at 5:45:23 AM UTC-4, jens.t...@gmail.com wrote: > > From within the view function (i.e. handling the incoming request) I issue > 5 subrequests one after the other. Doing so I noticed that the number of > subrequests was bound by the pool_size + max_overflow, hence my question > here and in the SQLA group. >
My confusion in your wording was that "It shouldn't work like that". Pyramid handles subrequests independently, so it will create a new session with a connection checked out from the pool, and then should close and return it at the end. I thought there may be something wrong with the connection pool, perhaps during startup or perhaps by the subrequest functionality, but looking at the subrequest source it doesn't look to spawn a new thread. How are you handling your session connection and cleanup? Are you using pyramid_tm? If so, are you using the `use_tween` on the invoke_subrequest to properly close each connection in the pool? If not, how are you cleaning up your connections? -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to pylons-discuss+unsubscr...@googlegroups.com. To post to this group, send email to pylons-discuss@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/pylons-discuss/742c3ea1-0637-4e5c-a6e7-3d10a39b3bdb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
