Comment 0 for bug 2047701
Revision history for this message
| Galen Charlton (gmc) wrote [XMPP] C drones do not directly terminate Jabber streams upon exit | #0 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
C service drones do not explicitly terminate their XMPP sessions by sending a "</stream:stream>" message prior to exiting (Perl services do). Instead, the socket just gets closed when the process ends.
This doesn't appear to be the end of the world, but it does cause "Connection failed: connection closed" noise in the Ejabberd logs that can mask true connection failures.
Looks like osrf_prefork_