Re: [twsocket] Connection Timeout
Hello, Did you check whether FDocStream is cleared after request is complete? Sometimes ICS version upgrades can lose backwards compatibility when announced otherwise. Regards, SZ On Mon, Oct 11, 2010 at 12:32 PM, Olaf van der Meer wrote: > Hello, > > I use an own derived object of THttpConnection. In this object are some > variables which are used for local processing. > The code has not been changed in years. I updated the ICS components and > mentioned the differences in create and destroing of the THttpConnection > object. > > There were no clear actions. The application trusted on the creation of new > objects when a new connection was made. > Now, I have added some clear actions and 'Connection: close' (for sure, if > I forget to clear something) to the header of the answer. > It works well now. > > Thanks for your help. > > Regards, > > Olaf van der Meer > > > > - Original Message - From: "Francois PIETTE" < > francois.pie...@skynet.be> > To: "ICS support mailing" > Sent: Monday, October 11, 2010 10:42 AM > Subject: Re: [twsocket] Connection Timeout > > > > now we have some problems with the webserver. >>> So the problem is: the old connection is reused and >>> it contains data which could not belong to the request. >>> >> >> What do you mean by "it contains data" ? The component handling a >> connection do not contain any data unless you added the data yourself and >> forgot to clear it at appropriate time. >> >> Are you able to reproduce this behavious using the demo webserver provided >> with ICS ? If yes, please provide the exact steps so that we can examine it. >> If not, can youy write a very simple, actually the most simple possible, >> sample code showing the issue you have ? >> >> Regards, >> -- >> francois.pie...@overbyte.be >> The author of the freeware multi-tier middleware MidWare >> The author of the freeware Internet Component Suite (ICS) >> http://www.overbyte.be >> >> -- >> To unsubscribe or change your settings for TWSocket mailing list >> please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket >> Visit our website at http://www.overbyte.be >> >> > > > -- > To unsubscribe or change your settings for TWSocket mailing list > please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket > Visit our website at http://www.overbyte.be > -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Connection Timeout
Hello, I use an own derived object of THttpConnection. In this object are some variables which are used for local processing. The code has not been changed in years. I updated the ICS components and mentioned the differences in create and destroing of the THttpConnection object. There were no clear actions. The application trusted on the creation of new objects when a new connection was made. Now, I have added some clear actions and 'Connection: close' (for sure, if I forget to clear something) to the header of the answer. It works well now. Thanks for your help. Regards, Olaf van der Meer - Original Message - From: "Francois PIETTE" To: "ICS support mailing" Sent: Monday, October 11, 2010 10:42 AM Subject: Re: [twsocket] Connection Timeout now we have some problems with the webserver. So the problem is: the old connection is reused and it contains data which could not belong to the request. What do you mean by "it contains data" ? The component handling a connection do not contain any data unless you added the data yourself and forgot to clear it at appropriate time. Are you able to reproduce this behavious using the demo webserver provided with ICS ? If yes, please provide the exact steps so that we can examine it. If not, can youy write a very simple, actually the most simple possible, sample code showing the issue you have ? Regards, -- francois.pie...@overbyte.be The author of the freeware multi-tier middleware MidWare The author of the freeware Internet Component Suite (ICS) http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Connection Timeout
now we have some problems with the webserver. So the problem is: the old connection is reused and it contains data which could not belong to the request. What do you mean by "it contains data" ? The component handling a connection do not contain any data unless you added the data yourself and forgot to clear it at appropriate time. Are you able to reproduce this behavious using the demo webserver provided with ICS ? If yes, please provide the exact steps so that we can examine it. If not, can youy write a very simple, actually the most simple possible, sample code showing the issue you have ? Regards, -- francois.pie...@overbyte.be The author of the freeware multi-tier middleware MidWare The author of the freeware Internet Component Suite (ICS) http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Connection Timeout
Olaf van der Meer wrote: > Hello, > > Recently we have updated the ICS components and now we have some > problems with the webserver. > In the old version every time a browser makes a request to the > webserver a new connection were created and connected, and afterwards > the connection were disconnected and destroyed. It depends entirely on the client/browser. Only if it either uses HTTP 1.0 without the "Connection: Keep-Alive" header or >= HTTP 1.1 with the "Connection: close" header the connection will be closed after each request, that is how HTTP works. > In the new version just one connection is created and connected (even > if the browser makes several requests to the server). See above, it has not changed. > The connection will be reused untill it expires so much seconds as set by the > property KeepAliveTimeSec of the webserver component. Only after the > KeepAliveTimeSecs the connection is disconnect and the object will be > destroyed. Yes, you can turn this feature off by setting both KeepAliveTimeSec and MaxRequestsKeepAlive to zero. > > So the problem is: the old connection is reused and it contains data > which could not belong to the request. Then it is your application that is buggy. > > I have tried to set the KeepAliveTimeSec to zero which should disable > the KeepAliveTime feature entirely (read from the svn-changelog), but > then the connection still stays connected. It is even worse. Now it > stays connected untill god knows how long. It is not predictable how > long the connection is active. Well, it's the same behaviour as in previous versions, there is no timeout specified, hence if a client requests a persistent connection it is not closed until the client disconnects or requests a connection close. > > I also tried to force the connection to close with the procedures > Close en CloseDelayed after the answer is send. But then the answer > is not send completely with half html pages as results. > > Do you have any suggestions how to handle this? Set the MaxRequestsKeepAlive to "1" (one). However your server application should be able to handle persistent connections. -- Arno Garrels -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
[twsocket] Connection Timeout
Hello, Recently we have updated the ICS components and now we have some problems with the webserver. In the old version every time a browser makes a request to the webserver a new connection were created and connected, and afterwards the connection were disconnected and destroyed. In the new version just one connection is created and connected (even if the browser makes several requests to the server). The connection will be reused untill it expires so much seconds as set by the property KeepAliveTimeSec of the webserver component. Only after the KeepAliveTimeSecs the connection is disconnect and the object will be destroyed. So the problem is: the old connection is reused and it contains data which could not belong to the request. I have tried to set the KeepAliveTimeSec to zero which should disable the KeepAliveTime feature entirely (read from the svn-changelog), but then the connection still stays connected. It is even worse. Now it stays connected untill god knows how long. It is not predictable how long the connection is active. I also tried to force the connection to close with the procedures Close en CloseDelayed after the answer is send. But then the answer is not send completely with half html pages as results. Do you have any suggestions how to handle this? Version of the webservercomponent before the update: THttpServerVersion = 142; After: THttpServerVersion = 722; And I use Delphi 2007. Thanks in advance Greetings, Olaf van der Meer ;XSO xBase Software Ontwikkeling. -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be