Hi!

Update: We finally solved our OX-Look crash problem!

OX-Look (up to 4.2.7) has a bug because when it reaches the timeout it
crashes rather then catch and report a timeout error!

With now over 310 users the problem was a timeout waiting for a
groupware response (actually postgres wasn't fast enough). We found this
only because since this week NO OX-Look user was able to sync his
appointments any longer.

Here some details about the involved data:
55.000 entries in 'prg_dates'
60.000 entries in 'prg_date_rights'
60.000 entries in 'prg_dates_members'

Deleted appointments go to del_dat* tables, so if someone syncs again
after e.g. month of no sync it must know what has been deleted in the
meantime. I think this is how those tables are used.
Details about the usage of these tables:
33.000 entries in 'del_dates'
42.000 entries in 'del_dates_members'

As you can see this is quite a some data. There is one group which has a
shared calendar with 25.000 entries!!!

Back to the topic. Last year we had some performance problem because OX
(at least the OX 0.8.0 and 0.8.2 - even if the 0.8.2 is a little bit
better) has as special feature by default. It's not using indexes on the
database tables. There was a discussion last year and I don't want to
argue again about that. If you are interested look for yourself.
To solve the performance problem I added indexes to several of the used
columns on each of the tables we use most.
This helped to solve all problems we had until 22. Dec. 2006 where I had
the problem that OX-Look was crashing when I tried to sync the private
calendar of a new user.
The guy from OX-Support had no idea and the answers on this mailinglist
and also the forum were not very helpfull.
Beside that the crash was also pointing to the wrong direction.

The problem, we finally found out yesterday, was that the 'del_dates'
and 'del_dates_members' were still not using indexes at all. So the
groupware started a query on postgresql that didn't finish in time and
OX-Look simply crashed!
After I added the same indexes I used already on the prg_date* tables on
the del_dates* tables it does work as it should.

It would be nice if the timeout that leads to the crash would be catched
properly in OX-Look...I think I will add a bugreport shortly.

If anyone encounters the same problem, add indexes on the tables
mentioned above.
The original mail (most of it) with the crash dump follows at the
bottom.

Kind regards,
Juergen Ulbts
---
IBIT - Groupware Administration
Carl von Ossietzky University, Oldenburg (Germany)



Am Fr 12.01.2007 10:06 schrieb JU <magog001 at web.de>:
>Hello!
>
>We have this problem sind end of december 2006 with two new groupware
>user which
>need the Connector to sync with their Windows PDAs.
>
>We've tested OXLook v3.8.9, v4.0.18, v4.2.3 and v4.2.5.
>
>The Groupware Server is still 0.8.0-6 as the currently available
>OpenSource
>0.8.2-x has an error at the project tasks (no access) which has been
>fixed on
>31.08.2006. This doesn't help when it's not released as OpenSource.
[..]
>Here is the first part of the OXLook v4.2.5 crash report:
>====================================
>EurekaLog 5.1.9
>
>Application:
>-------------------------------------------------------
>1.1 Start Date : Fri, 12 Jan 2007 09:44:33 +0100
>1.2 Name/Description: Microsoft Outlook
>1.3 Version Number : 10.0.6626.0
>1.4 Parameters :
>1.5 Compilation Date: Fri, 22 Dec 2006 15:46:37 +0100
>
>Exception:

>>---------------------------------------------------------------------------------------------------------
>2.1 Date : Fri, 12 Jan 2007 09:45:36 +0100
>2.2 Address: 012082C4
>2.3 Module : oxlook.dll
>2.4 Type : EAccessViolation
>2.5 Message: Zugriffsverletzung bei Adresse 012082C4 in Modul
>'oxlook.dll'.
>Lesen von Adresse 00000014.
>
>Active Controls:
>-------------------------------------------------
>3.1 Form Class : rctrl_renwnd32
>3.2 Form Text : Kalender - Microsoft Outlook
>3.3 Control Class:
>3.4 Control Text :
>
>Computer:
>[...]
>
>Operating System:
>------------------------------------
>5.1 Type : Microsoft Windows XP
>5.2 Build # : 2600
>5.3 Update : Service Pack 2
>5.4 Language: German
>[...]
>Call Stack Information:

>>------------------------------------------------------------------------------------------------------------------------------------
>|Address |Module |Unit |Class
>|Procedure/Method |Line |

>>------------------------------------------------------------------------------------------------------------------------------------
>| Running Thread: ID=3104; Priority=0;
>Class=thread_folder_element_retrieve
>|

>>|----------------------------------------------------------------------------------------------------------------------------------|
>|012082C4|oxlook.dll |SimpleXML.pas |TxmlNode
>|GetChildrenCount |190 |
>|0126F3D8|oxlook.dll
>|Unit_retrieve_element_from_folder.pas|thread_folder_element_retrieve
>|parseXML |402 |
>|0126EC34|oxlook.dll
>|Unit_retrieve_element_from_folder.pas|thread_folder_element_retrieve
>|parseXML |253 |
>|01272DB4|oxlook.dll
>|Unit_retrieve_element_from_folder.pas|thread_folder_element_retrieve
>|Execute |1262 |
>|01156666|oxlook.dll |classes.pas |
>|ThreadProc |9372 |
>|01132B61|oxlook.dll |system.pas |
>|_FreeMem |2466 |
>|01134D34|oxlook.dll |system.pas |
>|ThreadWrapper |11554|
>[...]
>====================================
>
>_______________________________________________
>User mailing list
>User at open-xchange.org
> http://www.open-xchange.org/cgi-bin/mailman/listinfo/user