| 2023-12-29 15:08:33 |
Galen Charlton |
bug |
|
|
added bug |
| 2023-12-29 15:50:42 |
Galen Charlton |
opensrf: importance |
Undecided |
Low |
|
| 2023-12-29 16:36:50 |
Galen Charlton |
tags |
|
pullrequest |
|
| 2023-12-29 16:41:30 |
Galen Charlton |
description |
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_child_exit() is where the client connection cleanup would be added. |
C service drones do not explicitly terminate their XMPP sessions by sending a "</stream:stream>" message prior to exiting voluntarily (as opposed to being terminated by the listener. Perl services do cleanly end their XMPP session upon self-exit. 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_child_exit() is where the client connection cleanup would be added. |
|
| 2023-12-29 16:41:42 |
Galen Charlton |
summary |
[XMPP] C drones do not directly terminate Jabber streams upon exit |
[XMPP] C drones do not directly terminate Jabber streams upon self-exit |
|
| 2023-12-29 16:45:51 |
Galen Charlton |
description |
C service drones do not explicitly terminate their XMPP sessions by sending a "</stream:stream>" message prior to exiting voluntarily (as opposed to being terminated by the listener. Perl services do cleanly end their XMPP session upon self-exit. 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_child_exit() is where the client connection cleanup would be added. |
C service drones do not explicitly terminate their XMPP sessions by sending a "</stream:stream>" message prior to exiting voluntarily (as opposed to being terminated by the listener). Perl services do cleanly end their XMPP session upon self-exit. 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_child_exit() is where the client connection cleanup would be added. |
|
| 2023-12-29 16:46:12 |
Galen Charlton |
description |
C service drones do not explicitly terminate their XMPP sessions by sending a "</stream:stream>" message prior to exiting voluntarily (as opposed to being terminated by the listener). Perl services do cleanly end their XMPP session upon self-exit. 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_child_exit() is where the client connection cleanup would be added. |
C service drones do not explicitly terminate their XMPP sessions by sending a "</stream:stream>" message prior to exiting voluntarily (as opposed to being terminated by the listener). Instead, the socket just gets closed when the process ends. (Perl services do cleanly end their XMPP session upon self-exit.)
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_child_exit() is where the client connection cleanup would be added. |
|
