[Kolab-devel] pfbcache.db locking problems

[Pieter Vanmeerbeek]

Hi,

I was wondering if anyone else got locking problems with gdbm pfbcache.db
file. If you create an appointment with > 14 resources, all set with
declines if conflicts, you can simulate it easily.

The lookup of freebusy info just stops as the database is locked by one of
the other resource handling threads, resulting in nt adding a calendar entry
for the resource. This following line is shown as extra info when I add
extra logging and create a dump of info gathered with the parse_url($url)
statement on line 467 of the kolabfilter/resmgr.php file : 


<b>Warning</b>:  dba_open(pfbcache.db,cd): Driver initialization failed for
handler: gdbm: Can't be writer in
<b>/ub-ver/ub-7.0.0/pkg/php4/lib/php/freebusy/freebusy
cache.class.php</b> on line <b>41</b><br />



kind regards,
Pieter

--
---------------------------------------------------
Event: 10 years Able 10: 1996 - 2006 - We are pleased to invite you, subscribe at http://www.able.be/10

aXs GUARD has completed security and anti-virus checks on this e-mail (http://www.axsguard.com)
---------------------------------------------------
Able NV: ond.nr 0457.938.087
RPR Mechelen