standalone.py running 24/7

[Zach]

Hey all!

When I start the server (via standalone.py) using WSS, it works fine in the beginning. A day passes, and when I go to my website, a WebSocket connection is established, but as soon as I send it any message it disconnects the user. I'm wondering if anything comes to mind when the server is run continuously: what potential areas should I investigate that would lead to an initially good server for the first couple hours, but not after a day (or maybe even 16 hours... I haven't pinpointed the time). I also don't know if it's solely time-based or if one incident occurs during such a long period of time.

Thanks! 

[Takeshi Yoshino]

Thanks for the report. I'll investigate it. Which module are you using? pyOpenSSL or standard ssl module.

Is anyone experiencing similar issue?

Takeshi

--
 
---
You received this message because you are subscribed to the Google Groups "pywebsocket" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pywebsocket...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Zach]

I now think it has to do with the SQL connection, not pywebsockets (based on the below link)

http://stackoverflow.com/questions/12444272/error-2006-mysql-server-has-gone-away-using-python-bottle-microframework-and

With a fix (or workaround) found at:

http://stackoverflow.com/questions/207981/how-to-enable-mysql-client-auto-re-connect-with-mysqldb

[Zach]

oh, and I'm using OpenSSL (just fyi).