RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1346179 - [Camel] Set default connection timeout to 90 seconds
Summary: [Camel] Set default connection timeout to 90 seconds
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: evolution-data-server
Version: 7.2
Hardware: Unspecified
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: Milan Crha
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-14 08:08 UTC by Anthony Symons
Modified: 2016-11-04 00:25 UTC (History)
4 users (show)

Fixed In Version: evolution-data-server-3.12.11-33.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-04 00:25:53 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
bt.txt requested in comment 1 (13.55 KB, text/plain)
2016-06-15 01:55 UTC, Anthony Symons 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2206 0 normal SHIPPED_LIVE evolution-data-server bug fix update 2016-11-03 13:23:16 UTC

Description Anthony Symons 2016-06-14 08:08:56 UTC 
Description of problem:

When Evolution is configured to access email via IMAP it appears to locally cache the IP of the remote server and use it in a way which is blocking inside the kernel. A "killall -9 evolution" is required to force the app to exit, and a restart of the app is required to collect more mail.

Version-Release number of selected component (if applicable):
evolution-3.12.11-15.el7.x86_64

How reproducible:
Every time

Steps to Reproduce:
1. Connect to an imap mail service and leave evolution viewing the mailbox
2. Move the imap server to a different IP and update dns (eg a different network view or a mail server on a dynamic IP)
3. Note that no new mail appears and you cant view unread mail.
4. Close evolution via the UI - notice it greys out but never closes.
5. killall evolution - notice that it does not close.
6. killall -9 evolution - notice it took the really big hammer to close it.

Actual results:
No new mail, cant close or kill app without kill -9

Expected results:
App fails to connect, trys again, resolves the host and new IP and connects to that. If it can not contact the server, not to get in to a state which requires kill -9.

Additional info:
If this is not a bug in evolution core but it can be identified which component has the bug feel free to move it.
Comment 1 Milan Crha 2016-06-14 09:19:21 UTC 
Thanks for a bug report. The IMAPx (and basically whole evolution-data-server) uses glib2/glib-networking for the connections, either directly or indirectly (through libsoup). There are set some timeouts for the connections, as far as I know.

Could you install debuginfo packages for the evolution-data-server, evolution, glib2 and glib-networking (make sure the versions match the binary package version), then run the evolution and get it into this "doesn't want to quit" state. When it's there, get the backtrace of it with this command:

   $ gdb --batch --ex "t a a bt" -pid=`pidof evolution` &>bt.txt

Please check the bt.txt for any private information, like passwords, email address, server addresses,... I usually search for "pass" at least (quotes for clarity only). It will show what the evolution does and why it doesn't want to quit.

Could you provide also the evolution-data-server package version, please?

By the way, you can also run `evolution --force-shutdown` to stop the evolution related processes. More recent evolution allows to quit gracefully when the quit is not done within a minute or so, by asking the user whether to wait or to quit immediately.
Comment 3 Anthony Symons 2016-06-15 01:53:25 UTC 
Hi Milan,

Thanks for looking in to this. Package versions:

evolution-3.12.11-15.el7.x86_64
evolution-devel-3.12.11-15.el7.x86_64

evolution-data-server-3.12.11-24.el7.x86_64
evolution-data-server-devel-3.12.11-24.el7.x86_64

glib2-2.42.2-5.el7.x86_64
glib2-devel-2.42.2-5.el7.x86_64

glib-networking-debuginfo-2.42.0-1.el7.x86_64
glib-networking-2.42.0-1.el7.x86_64

I'll attach bt.txt
Comment 4 Anthony Symons 2016-06-15 01:55:15 UTC 
Created attachment 1168122 [details]
bt.txt requested in comment 1
Comment 5 Milan Crha 2016-06-15 07:44:51 UTC 
Thanks for the update. You forgot to install debuginfo packages, thus the backtrace is missing line numbers and other valuable information which helps with debugging, but it also shows that one of the threads is waiting inside the call to g_socket_client_connect().

The Camel code (inside evolution-data-server) doesn't set any timeout for this connection, keeping there the default value, which is apparently no timeout at all. I changed this upstream for 3.21.3+ [1] and 3.20.4+ [2].

I'm not sure whether there would be any way to deal with this in a quicker way, maybe on the glib2 side.

[1] https://git.gnome.org/browse/evolution-data-server/commit/?id=4d23a81
[2] https://git.gnome.org/browse/evolution-data-server/commit/?id=594c548
Comment 9 errata-xmlrpc 2016-11-04 00:25:53 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-2206.html
Note You need to log in before you can comment on or make changes to this bug.