Curtis,


> What is consistent are the error codes and the call stack of thread 1
> in WAA.

Thread 1 is the main application thread, which basically is running the
listening socket for the application, which is why it alwys looks the same.
Don;t look at this, it's a red herring.

> FATAL ERROR LOG
> Error within the error handling!
> SYS Thread-ID: 1508

1508 is the system-id of the thread where the error is detected.

> Call Stack of Thread 3 (1508):
> <non constant name>(1286982308)

This where the error is detected.

> @WAA1JOBQUEUE@I@GETJOB(606)

This is a 'paused' thread waiting to service a request.

> Call Stack of Thread 8 (1728):
> @CGICHANNEL@I@CONNECT(109)
> @WAAGATEWAY@I@CGICONNECT(75)
> @WAA1REQUESTER@I@EXECUTE(177)

This is a thread where an incomming connection is being established.

Since the error occurs (or seems to) at different places, it is likely that
there is a memory corruption ocurring. You mentioned using SQL - what
library are you using to do this - ODBCDBE, SqlExpress or PGLib?

A common problem with SQL is the failure to properly destroy a reference to
a result-set when it is no longer used.  Using ODBCDBE for example, you
should provide an alias when running a query so you can destroy the
result-set later:

    using ODBCDBE
   
   USE (cSql_query) ALIAS (cAlias)
   ...
   (cAlias)->(dbCloseArea())

    Using PGLib
   
   oData := Sql( cSql )
   ...
   oData:destroy()

   etc.

Your problem could also be because you have called a C/C++ routine or
WinAPI function directly and not properly protected memory or tidied up, or
the routine you are calling is not thread-safe or has a memory leak.

Regards,

Phil Ide

*******************************************
*   Xbase++ FAQ, Libraries and Sources:   *
*   goto: http://www.idep.org.uk/xbase    *
* --------------------------------------- *
* www.xodc.org.uk - openSource Dev-Center *
*******************************************

Drive slower than your guardian angel can fly.

Thank you f or the pointers. We'll check these out.