Re: [Firebird-devel] FB1.5 RC6 CS - Lock manager error

[gustavo <gu...@mw...>]

I can reproduce this in a single processor box. Just let a long running
transaction/large fetch query running, connect using another instance and
try to query again. That´s it "lock manager out of room". I´m not sending
anything (like logs, etc) because you people are investingating the problem,
but I´m sure something is wrong with the win32 lock manager (yet).

----- Original Message ----- 
From: "Zelený Aleš" <az...@cs...>
To: <fir...@li...>
Sent: Tuesday, October 14, 2003 5:50 PM
Subject: RE: [Firebird-devel] FB1.5 RC6 CS - Lock manager error


> Hello,
>
> after long time (I don't have easy access to a SMP computer) I've done
some test (now on 2CPU system):
>
> Conditions:
>
> 2xzCPU system
> 2GB RAM
> FB 1.5 RC6 Classic server
> WinXP
> Restored backup of IB6.0 database.
> IB_SQL was used as app for tests.
> About databse:
>
> Database:  localhost:C:\fb\mydb.fdb, User: sysdba
> Database: localhost:C:\fb\mydb.fdb
>         Owner: SYSDBA
> PAGE_SIZE 8192
> Number of DB pages allocated = 277054
> Sweep interval = 0
> Forced Writes are ON
> Transaction - oldest = 176
> Transaction - oldest active = 215
> Transaction - oldest snapshot = 215
> Transaction - Next = 218
> Default Character set: WIN1250
>
>
> First tests:
> ~~~~~~~~~~~~
>
> Locks after services was started:
> 1_lockprint_svc_started.txt
>
> Locks after "lock manager out of room" error:
> 1_lockprint_lock_manager_err.txt
>
> Error to Fb log was written at filed  session disconnect time:
> 1_firebird.log
>
> SQL calls from apllication from connect to error:
> 1_IB_SQL_trace_lock_manager_err.TXT
>
>
> Second test:
> ~~~~~~~~~~~~
> Locks after services was started:
> 2_lockprint_svc_started.txt
>
> First app connected:
> 2_lockprint_1_connection.txt
>
> Second app connected:
> 2_lockprint_2_connections.txt
>
> First App open a select:
> 2_lockprint_openned_select_statement.txt
>
> First App fetching rows - lock manager error occured:
> 2_lockprint_lock_mgr_err_after_fetch_started.txt
>
> IB_SQL trace from failed session:
> 2_IB_SQL_trace_lock_manager_err.TXT
>
> IB_SQL trace from only connected session:
> 2_IB_SQL_trace_connected_seesion.TXT
>
> FB log - error was written on failed session disconnect.
> 2_firebird.log
>
> Notes:
> If tehre were only one App connecetd and fetching rows no error occured.
Folowing scenario cause error in same way - so it is possible to reproduce
this error.
>
> I have done more tests, some of then with terible results, like all
sessions disconneted after lock manager error and NT services were
restarted, but new connection failed at connect time due to "lock manager
out of room error". Unfortunmately i'm not able to reproduce this error.
>
> I'll found also another errors, so I'll try send them later.
>
> Here is table structure and number of rows:
> SEANCE_KEY                      (SERIAL) INTEGER Not Null
>                                 check (value > 0)
> SEANCE_PTR_PRIPAD               INTEGER Nullable
> SEANCE_PTRI_KONTAKT             INTEGER Nullable
> SEANCE_TYP                      (CISELNIK) VARCHAR(5) Not Null
> SEANCE_CALLID                   (V25) VARCHAR(25) CHARACTER SET WIN1250
COLLATE PXW_CSY Nullable
> SEANCE_ZACATEK                  TIMESTAMP Nullable
> SEANCE_KONEC                    TIMESTAMP Nullable
> SEANCE_SLIB                     TIMESTAMP Nullable
> SEANCE_VYSLEDEK                 (CISELNIK) VARCHAR(5) Not Null
> SEANCE_POZNAMKA                 (V32K) VARCHAR(32765) CHARACTER SET
WIN1250 COLLATE PXW_CSY Nullable
> SEANCE_STAV                     INTEGER Nullable
> SEANCE_BEG                      TIMESTAMP Nullable
> SEANCE_KDYVZNIK                 TIMESTAMP Nullable
> SEANCE_KDYZMENA                 TIMESTAMP Nullable
> SEANCE_APROBACE                 (V25) VARCHAR(25) CHARACTER SET WIN1250
COLLATE PXW_CSY Nullable
> SEANCE_WORKEY                   INTEGER Nullable
>
> Triggers on Table SEANCE:
> SET_SEANCE_KEY, Sequence: 0, Type: BEFORE INSERT, Active
> SEANCE_INSERT_VZNIMENA, Sequence: 3, Type: BEFORE INSERT, Active
> SEANCE_UPDATE_VZNIMENA, Sequence: 3, Type: BEFORE UPDATE, Active
>
>        COUNT
> ============
>
>       915633
>
> I hope this will help to fix lock manager bug. Please let' me know if it
was usefull test :-)
>
> Best regards Ales Zeleny
> ----------------------------------------------------------------------- 
> Ales Zeleny (OK1UUE)
> 6214 Central systems system support
> Ceska sporitelna a.s.
> Bubenska 1
> 170 00 Praha 7
> Czech Republic
> Email: az...@cs...
> tel: +420 2 66703 102 (Oracle: Symbols, MCI)
> tel: +420 2 66703 219
> ----------------------------------------------------------------------- 
> Due to technical difficulties tomorrow has been postponed indefinitely.
>
>
>