From: <az...@cs...> - 2003-09-26 14:36:01
|
Hello, > I thought lockmanager problems were solved in RC6 at least > > I dont have them anymore (1+ week problem free in production +/- 80 > connection on classic w2k SMP/ on a cluster). In changelog is a note about disabled automatic lock mem resizing - may be this could be the reason for different RC4 and RC6 behaviour. But I recived this error with 2 or 3 connections into database (page size 8192, a bit more than 2GB - nothing big) - so I expect for 3 clients lock shouldn't be overloaded (usually tehre are about 30 connected users for 8-10 hours). First time (with default values in config) I receive Lock mem error with one instance of my app and connected using "interbase performance monitor" (ibpm.exe - doesn't make senese in classic, just only connection test). 2x increasing lock mem size -> two instances of my app worked for a while until lock memm error. 4x increasing lock mem size -> two, somteimes three (not more) instances of my app worked for a while until lock memm error. More increasing has no change to amount of possible connections until Lock mem error. > some testing with lock_print showed that i'm actually using 1/4 of the > lockmemsize but i leave the size high. My fault, i forgot make print from lock_print :-( > RC6 server date (fb_inet_server.exe): 15-9-2003 11:08 > I used this version of Alex (after a fix): > Super - http://www.insi.yaroslavl.ru/fb/fb15rc6SS.tgz > or > Classic - http://www.insi.yaroslavl.ru/fb/fb15rc6CS.tgz > > Also Check your client side: (are you using the newest > fbclient.dll/gds32.dll ) I used files from RC6 package Firebird-1.5.0.3815_RC6_win32.zip. gds32.dll (the wrapper ) and fbclient.dll were copied into system32 directory on server and also on clients (application use IBO and originally was written use IB6 - gds wrapper is needed). Best regards Ales Zeleny ----------------------------------------------------------------------- Ales Zeleny (OK1UUE) Due to technical difficulties tomorrow has been postponed indefinitely. |