Bug 857016

Description of problem:
GConfd-2 clients fail to connect to the gconfd under heavy load. This leads to various error messages on the console.

Version-Release number of selected component (if applicable):


How reproducible:
Recursively spawning gnome-terminals is a sure shot way to reproduce this issue.


Steps to Reproduce:
1.
2.
3.
  
Actual results:

Errors like the one below:

Failed to summon the GConf demon; exiting.  Failed to contact
configuration server; some
possible causes are that you need to enable TCP/IP networking for
ORBit, or you have stale
NFS locks due to a system crash. See http://projects.gnome.org/gconf/
for information.
(Details -  1: Could not send message to GConf daemon: Message did
not receive a reply
(timeout by message bus))

and:


Failed to summon the GConf demon; exiting.  Failed to contact
configuration server; some
possible causes are that you need to enable TCP/IP networking for
ORBit, or you have stale
NFS locks due to a system crash. See http://projects.gnome.org/gconf/
for information.
(Details -  1: Ping to server error
IDL:omg.org/CORBA/COMM_FAILURE:1.0・・




Expected results:
No Error

Additional info:

* There is a gconfd instance listening to incoming connections
* The gnome-terminals keep spawning and talk to gconfd over ORbit2 sockets
* At some point in time, there is a contention from one of the gnome-terminal instance for a socket file, when it tries to make a connection:

 connect(12, {sa_family=AF_FILE, path="/tmp/orbit-partha/linc-146f-0-6730f10292203"}, 46) = -1 EAGAIN (Resource temporarily unavailable)

* gnome-terminal tries to connect once again, and when it fails this time around, it bails out with the error message that you see printed on screen.

This bug has been fixed in el5: https://bugzilla.redhat.com/show_bug.cgi?id=694451 and has been approved upstream (https://bugzilla.gnome.org/show_bug.cgi?id=662623)