Hi,
I'm experiencing something very strange, difficult to explain.
I wrote an application where users can connect to LDAP servers (about
each user connects to a different LDAP server) and execute a search.
* If the ldap server answers, everything is ok.
* If the search does not return, every user accessing %udat is hung. All
pages that do not access %udat work normally.
No message in apache logs. Restarting apache makes everything work again
until someone searches on a "bad" LDAP server.
I know the problem does not come from embperl itself : it's a low-level
network issue. But I don't understand why our frontend application (that
does not rely entirely on LDAP) is impacted this way : %udat accesses
are like "locked" globally.
Does this have to do with Apache::Session lock mechanism ? Could I relax
it while doing my LDAP calls and re-lock immediately after ?
I store things in %udat only after authentication. Could I globally
disable session locking and enable it only when writing to %udat ?
Thanks for your help,
--
Jean-Christophe Boggio -o)
embp...@thefreecat.org /\\
Independant Consultant and Developer _\_V
---------------------------------------------------------------------
To unsubscribe, e-mail: embperl-unsubscr...@perl.apache.org
For additional commands, e-mail: embperl-h...@perl.apache.org
