uhm, the problem is more subtle......... The main process of the scheduler is like a shell opened on that application....... it needs to reads models to see the scheduler definition. I guess that this means that it will also connect to all the databases defined in models, even if it will effectively send/receive commands only on the scheduler_db. Those "additional" connections are not needed as a matter of fact, but shouldn't block anything too: they're idle and never used.
Every spawned process (the one that will process the task) needs to execute models, else your task won't be able to access, e.g. "db", and, to be fair, they won't be able to "see" the tasks definitions in the first place. Those connections are used, but the connections are kept open just for the time the task gets processed (the spawned process dies as soon as the task finishes). Let me check if there is a workaround for the connections on the main process. I'll get back to you (at most in a few days) -- 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.
