Allan: " the client connections to 4D Server v17 are flakey and not as good as they've been in the past :-(“ That’s my impression, as well.
(To clarify, the posting was under my name but was for a client who, at the time, was subscribed via the digest.) Looking back over the 10+ years since V11, that version (which I’ve dubbed “4D Vista”) did set the low water mark but the dot releases of V11 went a long way to cleaning things up. I didn’t use V11, opting to join the fray with V12. The system my client was describing was started in V6, IIRC. It was moved to 2004, then V12/13 and then V15. V15 was a very solid version, with this issue arising only with V17R3. Networking is a topic that has come up on the 4D Forum over the years and the position that Thomas Maul seems to be that the code, as far as they are able to determine, is functioning as they expect so these are edge conditions that they’re not able to resolve. Thomas has indicates that 4D does want to resolve the issues so, if there is a way that the behaviors can be reproduced, they want to know about it. That's my interpretation of the message threads on the Forum over the years. -- Douglas von Roeder 949-336-2902 On Mon, Apr 29, 2019 at 6:56 PM Allan Udy (Golden Micro) <[email protected]> wrote: > > From: Douglas von Roeder <[email protected]> <[email protected]> > > To: 4D iNug Technical <[email protected]> <[email protected]> > Subject: Re: 4D 17.1 network issues > > I can confirm this same issue on v17r3 on Windows 64 bit client and server > running Windows Server 12r2 Datacenter. In addition, the server will > refuse connection until somebody touches the server admin window at which > point it will accept connections again. > > > Doug, for some months we've been having on-going issues with v17R3 server > (on Windows Server 12) autonomously set the 'Reject New Connections' button > on the Application Server page of the Server Admin window (so that it now > reads 'Accept New Connections'). > > When this happens we've found the only way that clients can reconnect > again is if we restart the 4D server. > > Having said all of this, we haven't seen the issue for a couple of weeks, > and that 'could' be related to changing back to the Legacy Network Layer -- > not confirmed yet. > > We've also had other Client disconnection issues where the 'New > Connections' button has not magically be changed, but client apps still > cannot connect. All in all our experience is that in some regards the > client connections to 4D Server v17 are flakey and not as good as they've > been in the past :-( > > Cheers, > Allan Udy > > Golden Micro Solutions Ltd, Blenheim, New Zealand > http://www.golden.co.nz <http://www.golden.co.nz> > > ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
