Skip over Navigation
dataflake.org
Home
Documentation
Software
Old Stuff
Bug Reporting
>>
dataflake.org
>>
Report Bugs
>>
Incorrect setResource call after an operation on a replica server.
Guest
Incorrect setResource call after an operation on a replica server.
|
Add new Issue
|
Search Issues
|
Add new Entry
|
Add Entry to: Incorrect setResource call after an operation on a replica server. (Resolved)
Issue
Incorrect setResource call after an operation on a replica server. (bug report)
Posted
2006/12/07 by Riccardo Lemmi (axa)
(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).
Full name
Email address
