Access Violation when disconnecting wodWebServer - WeOnlyDo Discussion board

Access Violation when disconnecting wodWebServer (wodFtpDLX / wodFtpDLX.NET)

by Paul Draper, Friday, December 09, 2005, 15:56 (6924 days ago)

Hi guys,

We have an application that contains multiple wodWebServerCom components. Each one is in its own thread with a seperate port number allocated. Each one returns different information.

Everything works fine, until we come to disconnect. Occasionally we get an access violation in TwodWebServerCom::get_Activated().

I've captured the following stack trace using AQTime:

[code]
First chance exception 0xC0000005 ACCESS_VIOLATION occurred at 0x0044B35D, write of address 0x00000041 at 0x0044B35D (in E:codeSAMSInterface Connection ManagerInterfaceConnectionManager.exe) 1868 14:22:09:671
0x0044B35D Wodwebservercomlib_tlb::TwodWebServerCom::get_Activated + 0x225 in InterfaceConnectionManager.exe 1868
0x003B3D78 Wodwebservercomlib_tlb::TwodWebServerCom::InvokeEvent + 0x298 in weonlydo.bpl 1868
0x4017346C Oleserver::TServerEventDispatch::Invoke + 0x80 in vcl60.bpl 1868
0x79014FD5 DllUnregisterServer + 0x12D21 in wodWebD.dll 1868
0x790148EF DllUnregisterServer + 0x1263B in wodWebD.dll 1868
0x790108E4 DllUnregisterServer + 0xE630 in wodWebD.dll 1868
0x790103A6 DllUnregisterServer + 0xE0F2 in wodWebD.dll 1868
0x790098C7 DllUnregisterServer + 0x7613 in wodWebD.dll 1868
0x77E12CA8 GetSysColor + 0x444 in USER32.DLL 1868
0x77E12DC5 GetSysColor + 0x561 in USER32.DLL 1868


Second chance exception 0xC0000005 ACCESS_VIOLATION occurred at 0x0044B35D, write of address 0x00000041 at 0x0044B35D (in E:codeSAMSInterface Connection ManagerInterfaceConnectionManager.exe) 1868 14:22:09:781
[/code]

We have other threads in our app supporting ftp, raw, telnet that also use wod components and we have not seen anything similar with these.

Any idea what could be causing this?

Thanks
Paul.


Complete thread: