Is there any inside limit for the number of session that version 9.52 could manage.

We are using an unlimited version of 9.52 on a  Windows Server 2003 32 bit 4 Gb ram, and when the sessions grow over about the number of 1500 the btrieve engine hangs returning status 3112, the only way to recover the situation is to kill the pervasive process using task manager, stopping and restarting the Pervasive services.

We are using only the transactional api, and none of the relational services.

We checked many configuration but none if changing.

Actually the server is configured to use system memory, max microkernel memory usage to 0, and a cache allocation size of 800 Mb, when the server hangs the system has plenty of system memory available and pervasive is using about 1.3 Gb.

Thanks for any info.

Flavio

When you say that Pervasive is "using 1.3GB", which number were you looking at?  The correct one to watch is NOT in TaskMan, but rather the "Virtual Bytes" reported ONLY in Performance Monitor (Process group, select NTDBSMGR.EXE as the process name, and Virtual Bytes as the setting). 

On a 32-bit system, this has a hard limit of 2GB.  Reaching this OS-defined maximum can cause the symptoms you mention.  Moving to a 64-bit OS with the same engine increases the maximum to 4GB.  Moving to the 64-bit version of PSQLv10 also increases the maximum -- 512GB, I think.