I think there is a problem with multithreading because of PySerial. Pyserial open a post connected to COM and COM is a resource that cannot be shared. In web2py every request is executed in its own thread so it is not obvious who open the COM, who closes it and how conflicts are avoided.
Please tell us more of what you are doing. The best solution may be not to use pyserial in a web2py problem but use it in a single bachground process that talks to web2py via queued messages. Massimo On Apr 16, 2:13 am, aabelyakov <[email protected]> wrote: > I do not use os.chdir or explicit calls to thread module. > I'm using PySerial and after the error COM port remains open. > To close it, I restart the web server. > How to avoid this? > > On 15 ÁÐÒ, 22:46, mdipierro <[email protected]> wrote: > > > > > Do you use os.chdir or explicit calls to the thread module in your > > code? > > > On Apr 15, 12:15špm, aabelyakov <[email protected]> wrote: > > > > During my application error occurs and it stops giving error ticket. > > > > How can I in my application to return the resources of the operating > > > system > > > (eg close the COM port) šbefore the error ticket not to restart the > > > web server? > > > > Excuse my bad English... > > > > Regards- óËÒÙÔØ ÃÉÔÉÒÕÅÍÙÊ ÔÅËÓÔ - > > > - ðÏËÁÚÁÔØ ÃÉÔÉÒÕÅÍÙÊ ÔÅËÓÔ - > > -- > Subscription settings:http://groups.google.com/group/web2py/subscribe?hl=en
