The problem only occurred when I was inserting rows into a MySQL table that had a guid (char(36)) as the primary key. In my SQLAlchemy setup, I assigned uuid.uuid1() to be the default for these columns, so python was generating the guid, and it is sent to the server.
I first found success when I moved the guid generation to the MySQL server side. I let MySQL generate the guid using its uuid() function. Everything worked at that point. Now I do not understand the next part. I changed my code back to how it originally was, with python generating the guid, and now everything works. I don't have any clue what is going on at this point. It works, but I don't know why. When I call the broken function referenced above, it works now, but nothing in the function's code has changed, I have been using a test stub function this whole time so I know the code has not changed. On Mar 5, 9:50 am, Bryan <[email protected]> wrote: > Found some more info here:http://hea-www.harvard.edu/~fine/Tech/addrinuse.html > > Apparently, pylons+paste is stalling when it comes to the server > sending its FIN packet to tell the client the transaction is done. It > does not happen when I use SimpleXMLRPCServer and ThreadingMixIn from > the standard library, so it must be something higher in the stack like > paste serve or something. > > I still don't understand how accessing MySQL through SQLAlchemy could > be the trigger for these kinds of network issues??? > > On Mar 5, 9:33 am, Bryan <[email protected]> wrote: > > > I have moved my code out of Pylons and into a typical SimpleXMLRPC > > server. It works fine there. This problem is somewhere in the pylons/ > > WSGI stack. > > > On Mar 4, 2:10 pm, Bryan <[email protected]> wrote: > > > > The problem seems to be that the server is supposed to send a couple > > > more confirmation packets, but does not for 5 minutes. So the client > > > is correct in waiting: it has not received the last few packets of the > > > transaction yet, even though it has received the actual xmlrpc data. > > > > I have seen a couple of posts on the internet about the "socket.error: > > > (98, 'Address already in use')" problem, but have never seen an > > > explanation or solution. Has anyone run into this problem? > > > > On Mar 4, 1:53 pm, Wichert Akkerman <[email protected]> wrote: > > > > > Previously Bryan wrote: > > > > > Using wireshark on the client side, the xmlrpc data is actually > > > > > getting back to the client right away. Then there is the large pause > > > > > (always right around 5 minutes) > > > > > Perhaps you are sending an incorrect Content-Length header and the > > > > client is waiting for more data to arrive? > > > > > Wichert. > > > > > -- > > > > Wichert Akkerman <[email protected]> It is simple to make > > > > things.http://www.wiggy.net/ It is hard to make things > > > > simple. > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
