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.
It does work just fine in 4D standalone but hangs the 4D Client in client server mode.
I have verified this problem, and it is a 4D bug. But I have a new beta version that fixes this by spawning a new process in the shell and then calling into the Active4D housekeeper from that process. That way the process is global and queries work as expected on Client.
Yes, I am in need for this and appreciate your quick response.
What are the risks involved with you new beta : major other changes ?
I don't see any risks. I have added a ton of new features, but these should not affect existing code. More importantly, I have fixed a few nasty bugs.
Reposting this. Is the 4D bug in the 4D web server or does it also affect A4D under ITK based servers?
Thanks,
Brad
