S
Stefan Marquardt
Guest
Now i have an environment where i can test all things, just restarted the server with automatically startup of database and appservers. The last line from db log is: [2014/10/14@09:53:13.865+0200] P-3672 T-3604 I BROKER 0: (12815) Lock table hash table size (-lkhash): 13063 The next lines should be: [2014/09/15@10:28:30.098+0200] P-20324 T-9804 I BROKER 0: (12816) Maxport (-maxport): 5000 [2014/09/15@10:28:30.099+0200] P-20324 T-9804 I BROKER 0: (12817) Minport (-minport): 3000 but they are missing, _mprosrv stops working. Client connect hangs. After some struggling with windbg i got these stacks from __mprosrv: Thead 0: ntdll!ZwWriteFile+0x15 kernel32!WriteFile+0x4a _mprosrv!bkWriteMessage+0x32 _mprosrv!dbLogMessage+0x335 _mprosrv!drFetch_DB+0x134 _mprosrv!msgout+0x201 _mprosrv!msgnCB+0xb9 _mprosrv!msgCB+0x1d _mprosrv!dsmMsgnCallBack+0x59 _mprosrv!dbContextWriteOptions+0x1568 _mprosrv!dsmContextWriteOptions+0x20 _mprosrv!doserve+0x73a _mprosrv!main+0xb2 _mprosrv!__tmainCRTStartup+0x10f kernel32!BaseThreadInitThunk+0x12 ntdll!RtlInitializeExceptionChain+0x63 ntdll!RtlInitializeExceptionChain+0x36 Thread 1: ntdll!ZwWaitForMultipleObjects+0x15 kernel32!BaseThreadInitThunk+0x12 ntdll!RtlInitializeExceptionChain+0x63 ntdll!RtlInitializeExceptionChain+0x36 Thread 2: ntdll!DbgBreakPoint kernel32!BaseThreadInitThunk+0x12 ntdll!RtlInitializeExceptionChain+0x63 ntdll!RtlInitializeExceptionChain+0x36
Continue reading...
Continue reading...