• Server crashes with xe:jdbcQuery and DomSQL

    By Philipp Bauer 1 decade ago

    We encounter server crashes with DomSQL.
    I use a xp:viewPanel with a xe:jdbcQuery. As i could see it mainly happens when there is a “JOIN” in the SQL-Statement.
    Also, it happens sooner, the more entries are in the view.

    The server is 8.5.3 FP4.
    I was able to reproduce it with 8.5.3FP2 and 9.0, too.
    ExtLib Version is 853.20121217-1354.

    In the NSD log file there is a “FATAL” StackTrace, please note the last 4 lines:

    thread 22/67: [ nHTTP: 1300: 05ac] FATAL THREAD

    FP=0x1c1e0148, PC=0x76e212fa, SP=0x1c1e0148

    stkbase=0x1c1f0000, total stksize=4194304, used stksize=65208

    EAX=0x00000041, EBX=0x00000000, ECX=0x1c1df122, EDX=0x7FEE0864577

    ESI=0x000927c0, EDI=0x00000b64, CS=0x00000033, SS=0x7FE0000002B

    DS=0x00000000, ES=0x00000000, FS=0x00000000, GS=0x7FE00000000 Flags=0x00000287

    [ 1] 0x76e212fa ntdll.ZwWaitForSingleObject+10 (1,3,258,1c1e2ec0)
    [ 2] 0x7FEFCF210DC KERNELBASE.WaitForSingleObjectEx+156 (0,1c1e3498,0,b64)
    @[ 3] 0x00ea9c74 nnotes.OSRunExternalScript+4164 (3,0,312c4a4,3)
    @[ 4] 0x00ea3b41 nnotes.FRTerminateWindowsResources+2277 (16D6E6562616766,e470e2,66736e2e,25356c5)
    @[ 5] 0x00ead2de nnotes.OSFaultCleanupExt+622 (0,ea2edb,150014,31305b0)
    @[ 6] 0x00eadd55 nnotes.OSFaultCleanup+29 (0,25711a6,0,600004)
    @[ 7] 0x00ec78ce nnotes.OSNTUnhandledExceptionFilter+626 (1c1e5cf0,0,1,0)
    [ 8] 0x76d49460 kernel32.UnhandledExceptionFilter+352 (1c1e5cf0,6,0,7FE00000001)
    [ 9] 0x76e63398 ntdll.MD5Final+7656 (1c1e6930,1005cc0b,1c1e6440,7FEFDCEABF5)
    [10] 0x76de85c8 ntdll.__C_specific_handler+156 (1c1f0000,1c1eff90,1c1eff90,76f12dd0)
    [11] 0x76df9d2d ntdll.RtlDecodePointer+173 (1c1f0000,76dbdf08,12f00,0)
    [12] 0x76de91cf ntdll.RtlUnwindEx+3007 (1c1e6930,1c1e6440,0,0)
    [13] 0x76e21248 ntdll.KiUserExceptionDispatcher+46 (1c1e6de0,57fd612,1c1e6c90,ffffffff)
    [14] 0x2ae7311f domsql+12575 (2af92e88,2af7d1d8,2af7d1d8,2af92e88)
    [15] 0x2aef79fb domsql.JNI_OnUnload+496059 (1c1e9e30,2af7d1d8,0,2af5eda8)
    [16] 0x2aef85a9 domsql.JNI_OnUnload+499049 (2af7d1d8,1a62e728,0,2bade450)
    [17] 0x2aef8782 domsql.JNI_OnUnload+499522 (0,1,1c1e9e30,FFFFFFFFFFFFFDF)

    • By Tommy Valand 1 decade ago

      I think the driver being used contains the defects mentioned here:
      http://webcache.googleusercontent.com/search?q=cache:4NK03y_j_LMJ:www2.sqlite.org/cgi/src/timeline&client=opera&hl=en&gl=no&prmd=ivns&strip=1

      The defects are related to queries on virtual tables with DISTINCT or JOINs. Hopefully someone still maintains this project and updates the driver.

      • By Philipp Bauer 10 years ago

        I updated the driver to 3.8.4.3
        Same issue…