Bug 1851074 Comment 1 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

If there are connection issues, [this](https://searchfox.org/comm-central/rev/c16e3927b9a402cc7ac2f9b158a636598140ee8e/mailnews/db/gloda/modules/MimeMessage.jsm#24) is called with an error code (2152398878), but not [this](https://searchfox.org/comm-central/rev/c16e3927b9a402cc7ac2f9b158a636598140ee8e/mailnews/db/gloda/modules/MimeMessage.jsm#92). So the connection is terminated, but the streaming process is not notified.

A second attempt will be skipped, because [this](https://searchfox.org/comm-central/rev/c16e3927b9a402cc7ac2f9b158a636598140ee8e/mailnews/db/gloda/modules/MimeMessage.jsm#228) returns an ongoing streaming process, which however will never return (because it is already dead), even if the connection is becoming stable again. So even if the connection is stable again, any message which was attempted to be streamed while the connection was unstable, will not be streamed until next restart.

Only gloda is affected. Displaying a message in the UI will work after the connection is stable again.

If the system is set to offline mode, [this](https://searchfox.org/comm-central/rev/c16e3927b9a402cc7ac2f9b158a636598140ee8e/mailnews/db/gloda/modules/MimeMessage.jsm#259) throws, but is never caught in (here](https://searchfox.org/comm-central/rev/c16e3927b9a402cc7ac2f9b158a636598140ee8e/mail/components/extensions/parent/ext-messages.js#380-389).
If there are connection issues, [this](https://searchfox.org/comm-central/rev/c16e3927b9a402cc7ac2f9b158a636598140ee8e/mailnews/db/gloda/modules/MimeMessage.jsm#24) is called with an error code (2152398878), but not [this](https://searchfox.org/comm-central/rev/c16e3927b9a402cc7ac2f9b158a636598140ee8e/mailnews/db/gloda/modules/MimeMessage.jsm#92). So the connection is terminated, but the streaming process is not notified.

A second attempt will be skipped, because [this](https://searchfox.org/comm-central/rev/c16e3927b9a402cc7ac2f9b158a636598140ee8e/mailnews/db/gloda/modules/MimeMessage.jsm#228) returns an ongoing streaming process, which however will never return (because it is already dead), even if the connection is becoming stable again. So even if the connection is stable again, any message which was attempted to be streamed while the connection was unstable, will not be streamed until next restart.

Only gloda is affected. Displaying a message in the UI will work after the connection is stable again.

If the system is set to offline mode, [this](https://searchfox.org/comm-central/rev/c16e3927b9a402cc7ac2f9b158a636598140ee8e/mailnews/db/gloda/modules/MimeMessage.jsm#259) throws, but is never caught in [here](https://searchfox.org/comm-central/rev/c16e3927b9a402cc7ac2f9b158a636598140ee8e/mail/components/extensions/parent/ext-messages.js#380-389).

Back to Bug 1851074 Comment 1