Norman Rasmussen wrote: > > Got the logs -- when the transport stops logging in, does it still > respond to service discovery, etc? Can you reproduce the logs of where > you tried to logout/login to poke the transport to disconnect/re-connect.
Haven't found a means to reproduce it at will but it has been periodically happening. I've got two instances of it in the log file at this point though. Haven't tried checking service discovery, I'll give it a shot prior to restarting the process next time (assuming the requested changes don't fix it, see below). > Something else I noticed, is that "yahoo.localhost/registered" is the > entry on your roster. Now "/registered" was removed a long time back, > so you probably want to remove the entry and re-register with the > transport so the the correct entry goes back. (This should re-init your > subscriptions too). I'm not sure how important is it to have the > resource removed, but running with "/registered" isn't a supported > configuration anymore. I'd been using the c-based transport up until just a few months ago. Switched to the python based one and didn't change anything. I've now removed it and registered again. -- Jamin W. Collins --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "py-transports" 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/py-transports?hl=en -~----------~----~----~----~------~----~------~--~---
