Skip over Navigation

dataflake.org

Home Documentation Software Old Stuff

Guest

Incorrect setResource call after an operation on a replica server. | Add new Issue | Search Issues | Add new Entry |

Incorrect setResource call after an operation on a replica server. (Resolved)

Request	LDAP User Folder -- bug report -- by Riccardo Lemmi (axa)
Posted on	Dec 7, 2006 10:18 am
Subscribe	Enter your email address to receive mail on every change to this issue.

Entries (Latest first)

	Resolve by Jens Vagelpohl on Dec 10, 2006 3:50 pm
	`Thanks for the idea, Riccardo. My implementation looks slightly different, but the end result is the same.`


	Comment by Jens Vagelpohl on Dec 7, 2006 10:54 am
	`I'll be happy to take a look at the patch. This is indeed undesirable behavior.`


	Initial Request by Riccardo Lemmi (axa) on Dec 7, 2006 10:18 am
	(I am not sure if it is really a bug) The problem: we have a LDAP Service configured with a master and 2 replica servers. We configured LDAPUserFolder to use the replica but caused by a write operation a ldap.REFERRAL exception is launched. After the call to handle_referral the connection remains on the master server and never fall back to the original one until we restart Zope. We have a patch that correct this behavior avoiding to set the referral server as default server (setResource in _connect).