I've seen the same problem here. I had to back my page sizes down from 1000 to 100 then to 20 to keep the ssl connection stable. This happens randomly with Active Directory as well... Any help would sure be appreciated.
On Wed, January 31, 2007 9:56 am, Si Smith wrote: > Erik, > > That is exactly the issue that I get. I am not sure that it > is related to particular entries since the problem "moves" if > I change the page size for paged responses; it was also > repeatable on a different directory with different data. > > I guess it is some weird interaction between SSL and LDAP > since the problem does not occur with a plain connection. > > Did you get a fix for this? > > Regards, > > Simon > > Erik Ableson wrote: >> This is interesting since I have a setup here with exactly the same >> issue. Side notes : >> >> The directory is ADAM, the problem only appears in large data sets being >> returned over SSL (regular LDAP on 389 works OK). I'm beginning to think >> that it's related to specific entries since a couple of times it's died >> on the same object, but that may just be chance. But the consistent >> signature is the 00 84 where I'm expecting a 30 84. >> >> Entry that works : >> Net::LDAPS=HASH(0x1db33b8) received: >> >> 30 84 00 00 01 B5 02 01 02 64 84 00 00 01 AC 04 0........d...... >> 49 43 4E 3D 4E 61 73 73 69 72 61 20 43 68 69 6B ICN=Nassira Chik >> 68 2C 4F 55 3D 45 58 43 48 41 4E 47 45 32 30 30 h,OU=EXCHANGE200 >> >> but dies on the next entry: >> Net::LDAPS=HASH(0x1db33b8) received: >> >> 00 84 00 00 01 A7 02 01 02 64 84 00 00 01 9E 04 .........d...... >> 47 43 4E 3D 44 61 76 69 64 20 4C 75 63 61 73 2C GCN=David Lucas, >> 4F 55 3D 45 58 43 48 41 4E 47 45 32 30 30 30 2C OU=EXCHANGE2000, >> >> I'm going to double check the ASN1 version, but I seem to remember that >> it was updated relatively recently. >> >> Cheers, >> >> Erik >
