Hi All;

Would anyone have an idea why periodically the web server will hang up (Not
Responding according to the Task Manager) when it is trying to fulfill two
requests at the same time?

It seems to happen when one request takes about 30-40 seconds to complete
and then a different request is received from a different worker thread.

It seems like the two threads collide to hang up the server.
I could happen six times in one day, and yet at most all other times the
same procedures work fine without hanging up the server.

In the StartWAA.bat file:
SET WAA_WORKERTHREADS=6
SET WAA_HOST=localhost
SET WAA_PORT=1024
SET WAA_TRACE=OFF
SET WAA_DEVMODE=OFF
SET WAA_INTERNAL_LOG=ON

Could the second thread be trying to access a file or record locked by the 
first thread?
Do you specify workareas by number?

Bruce - thanks for a suggestion.

Unfortunately, there is no file locking going on with the opened DBF by any
thread.

There may be a record lock taking place to add a new record in one thread
while another thread is skipping through a query.
Could that be causing a problem?

The application does not specify work areas by numbers.
It refers to the open work areas by their alias name.

You open DBF's with the "new area" parameter, I assume?
FILE->(dbappend()) locks the appended record when it is created, but just 
that record.

Yes, the DBFs are opened using "new" parameter.

Allen,

What version of WAA are you talking about ?

Could this be the infamous hanging worker-problem
from WAA 1.5/WAA 1.6

Regards,
Frans Vermeulen

> Hi All;
>
> Would anyone have an idea why periodically the web server will hang up 
> (Not
> Responding according to the Task Manager) when it is trying to fulfill two
> requests at the same time?
>
> It seems to happen when one request takes about 30-40 seconds to complete
> and then a different request is received from a different worker thread.
>
> It seems like the two threads collide to hang up the server.
> I could happen six times in one day, and yet at most all other times the
> same procedures work fine without hanging up the server.
>
> In the StartWAA.bat file:
> SET WAA_WORKERTHREADS=6
> SET WAA_HOST=localhost
> SET WAA_PORT=1024
> SET WAA_TRACE=OFF
> SET WAA_DEVMODE=OFF
> SET WAA_INTERNAL_LOG=ON
>
>

Hi Frans;

I'm using WAA 1.90.331