RE: Connection is broken, cannot receive request reply

2017-11-22 Thread Allan Udy via 4D_Tech
and restart. Customer is starting to get a bit grumpy about this and we're struggling to work out a solution to the problem. :-( Allan Udy David Ringsmuth<davidi...@gmail.com> wrote: Date: Wed, 15 Nov 2017 11:46:01 -0600 Subject: RE: Connection is broken, cannot receive request

RE: Connection is broken, cannot receive request reply

2017-11-15 Thread David Ringsmuth via 4D_Tech
to open a tech support case… Thanks! David Ringsmuth From: Alan Chan via 4D_Tech Sent: Tuesday, November 14, 2017 8:59 PM To: 4d_tech@lists.4d.com Cc: Alan Chan Subject: Re: Connection is broken, cannot receive request reply Just curious, 4 seconds for idle connections timeout? Alan Chan 4D

Re: Connection is broken, cannot receive request reply

2017-11-14 Thread Alan Chan via 4D_Tech
Just curious, 4 seconds for idle connections timeout? Alan Chan 4D iNug Technical <4d_tech@lists.4d.com> writes: >SET DATABASE PARAMETER(54;4)// Idle connections timeout ** 4D Internet Users Group (4D iNUG) FAQ:

RE: Connection is broken, cannot receive request reply

2017-11-14 Thread David Ringsmuth via 4D_Tech
iNug Technical Cc: Timothy Penner Subject: RE: Connection is broken, cannot receive request reply > On our client network we do have a managed switch, but on our test network we > don’t. > The same error happens on both networks. Have you found a network where the error does NOT occur

RE: Connection is broken, cannot receive request reply

2017-11-14 Thread Timothy Penner via 4D_Tech
> On our client network we do have a managed switch, but on our test network we > don’t. > The same error happens on both networks. Have you found a network where the error does NOT occur? If you have reproducible sample that causes the issue on multiple networks then then it sounds like the

RE: Connection is broken, cannot receive request reply

2017-11-13 Thread David Ringsmuth via 4D_Tech
, cannot receive request reply Hi David, Do you have a managed switch on this network?, it is possible for a switch to close a connection with no traffic, which could also result in this message. The usual wisdom dictate having the timeout set to less than the switch/router timeout to prevent