Furhter analysis has shown that what hangs the system is the first query to the 4D database from within the "On Session End" method.
I don't know why that hangs in client/server mode, but it is a fact. It seems that the client does not receive an answer from the process started on 4D server that handles the database request.
Reposting this. Is the 4D bug in the 4D web server or does it also affect A4D under ITK based servers?
I haven't tested it, but I'm pretty sure it will affect both, because the issue is that my internal housekeeping process is being treated as a local process by 4D.
In any case the mechanism is going to change for both.
Thanks. This might explain some random request freezes we are seeing.
best,
Brad
