Re: Memory access violation on multiprocessor NT 4.0 (ITS#871)

["Jim Hud" <jdhz@btinternet.com>]

What happens if you restrict slapd to one processor using
SetProcessAffinityMask ?


----- Original Message -----
From: <jwirecki@paradyne.com>
To: <openldap-its@OpenLDAP.org>
Sent: Thursday, November 02, 2000 4:56 PM
Subject: Memory access violation on multiprocessor NT 4.0 (ITS#871)


> Full_Name: Jerzy Wirecki
> Version: 2.0.6
> OS: NT 4.0 sp5
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (135.90.24.1)
>
>
> When running slapd 2.0.6 linked with BerkeleyDB 3.1.17 on
> multiprocessor NT 4.0, memory access violation is generated
> in libdb31.dll. If, however, slapd is built with only
> 1 worker thread (macro SLAP_MAX_WORKER_THREADS in slap.h
> set to 1), it runs OK.
>
> This problem looks to me like threads synchronization issue;
> when requests are serialized by slapd, everything is
> fine.
>
> I couldn't reproduce the problem on a single-processor system
> (probably, because a single-processor system provides a less
> stressful environment for testing threads synchronization).
>