Page 1 of 1

Scalix Server Warning "Debug message for Lab use :"

Posted: Tue Sep 25, 2007 6:19 am
by nuno.mesquita
Does anyone know what this means??
Every time i run omshowlog i have many warnings like this.
I have a Scalix community version 11.1


Code: Select all

WARNING                        Browser       (Mime_Browser  ) 09.25.07 09:49:04
[OM 24070] Debug message for Lab use :
ct_ReadContentRec - multiple recs read: 102 (pid = 23953)


WARNING                        Browser       (Mime_Browser  ) 09.25.07 09:49:04
[OM 3544] More records than expected read during ct_ReadContentRec operation.

        <- /build/11.1.0/src/lib/ombase/sfl/sfl_Blcked.c:1394[100,28875]
        <- /build/11.1.0/src/lib/ombase/sfl/sfl_Blcked.c:1697[100,28875]
        <- /build/11.1.0/src/lib/ombase/sfl/sfl_Blcked.c:1394[100,28875]
        <- /build/11.1.0/src/lib/ombase/sfl/sfl_Blcked.c:1697[100,28875]
        <- /build/11.1.0/src/lib/ombase/sfl/sfl_Blcked.c:1394[100,28875]
        <- /build/11.1.0/src/lib/ombase/sfl/sfl_Blcked.c:1697[100,28875]
        <- /build/11.1.0/src/lib/ombase/sfl/sfl_Blcked.c:1394[100,28875]
        <- /build/11.1.0/src/lib/ombase/sfl/sfl_Blcked.c:1697[100,28875]
        <- ct_FindRecNum 3001 RecNum=91
        <- /build/11.1.0/src/lib/ombase/sfl/sfl_Blcked.c:1394[100,28875]
        <- /build/11.1.0/src/lib/ombase/sfl/sfl_Blcked.c:1697[100,28875]
        <- /build/11.1.0/src/lib/ombase/sfl/sfl_Blcked.c:1394[100,28875]
        <- /build/11.1.0/src/lib/ombase/sfl/sfl_Blcked.c:1697[100,28875]
        <- /build/11.1.0/src/lib/ombase/sfl/sfl_Blcked.c:1394[100,28875]
        <- /build/11.1.0/src/lib/ombase/sfl/sfl_Blcked.c:1697[100,28875]
        <- /build/11.1.0/src/lib/ct/ct_readc.c:417[100,3544]

Posted: Wed Sep 26, 2007 7:40 am
by gren
Recently, we implemented some optimisations in accessing Scalix containers. This diagnostic message was added to detect where the old method would have worked out faster and then try and figure out why and improve the algorithm more.
The message probably should have been reported at a lower level, and indeed for the upcoming 11.2 release it will be reported as a "MINOR EVENT" which you typically won't see unless you increase the logging level.

Regards,
Gren.