Closed
Bug 11098
Opened 26 years ago
Closed 26 years ago
LDAP error on close
Categories
(Directory Graveyard :: PerLDAP, defect, P3)
Directory Graveyard
PerLDAP
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: leif, Assigned: leif)
Details
From: bloch@netscape.com (Max Bloch)
I am seeing an LDAP error on closing a connection. The message is "Bad parameter
to an LDAP routine" and it
definitely is happening somewhere inside PerLDAP "close" (there is no error
condition immediately prior to
the close). It does not appear to have any damaging consequences, though.
| Assignee | ||
Comment 1•26 years ago
|
||
More from Max:
Here's what I found:
(a) perform several operations on the $entry and check for error condition after
each one:
$ldap->printError() if $ldap->getErrorCode();
No errors
(b) $ldap->update( $entry );
check for errors:
$ldap->printError() if $ldap->getErrorCode();
No errors
(c) $ldap->close;
$ldap->printError() if $ldap->getErrorCode();
Result is:
"Bad parameter to an LDAP routine"
| Assignee | ||
Updated•26 years ago
|
Status: NEW → ASSIGNED
| Assignee | ||
Updated•26 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
| Assignee | ||
Comment 2•26 years ago
|
||
For now, this will not work (the LD connection handle is gone after the close).
We've changed the error handling so at least you won't get a funky error
message. We'll add some functionality for the v2.0 version, probably caching the
last error code in the Conn:: object.
You need to log in
before you can comment on or make changes to this bug.
Description
•