I was wondering if you had the issue again, maybe solved this or have more intel?
Our company activated the new network layer (NNL) in our 4D v17 enviroments, 2 weeks ago by default. Mainly because this is the new standard an because of issues in the legacy layer (we have alot of strange SQL, null point errors in legacy).
Honestly last time we activated the NNL was years ago in v15R versions and early v16. I sometimes still have a nightmare from the issue when more than 32 clients would connect and the perfomance dropped to a dead stop and no one else could connect. After 15 years I have alot more nightmares ofcourse not always 4D fault. :mrgreen:
Our online products consist of five hosted 4D 17.3hf1 Servers, 1000+ unique users (web and desktop). All running on windows server 2016 and the desktops Windows 2016 RDS.
Today on one our 4D Servers (the biggest of the five, 130 GB datafile with 500 MB structure) Around 90-100 4D clients connections, the clients became extremely slow. Alot of users got disconnected. No users could connect to the server. We closed 4D server normally en started it normally and the issue was gone.
Last week I already reverted back our biggest On-Premise customer (daily 136, 4d clients) back to legacy after one day! They have alot of migrating users switching from networks the whole day (ofcourse not logging out the system when they unplug). So in the old legacy they would simply crash the connection but in the NNL they pile up as sleeping users wich no one can drop and taking up free 4D licenses (I had 8 users in one day). Combined with a bug on our side that we prevent the same user from connecting again when registred made it impossible on that site.