![]() ![]() So if you are looking for the modern releases of Abyss Web Server, please visit. This is an important problem.The software described and available for download in this site is the last open source version of Abyss Web Server: In 2001, Abyss Web Server became closed source and subsequent versions were and continue to be published by Aprelium Technologies (a company founded by Abyss Web Server's original author). I hope this will be enough to reduce the number of connections. Thank you to the support of Aprelium (Abyss)! But lowering it as much, I do not know if it will not cause other problems … By dropping to 30 seconds (the minimum value apparently), it already reduced significantly the number of connections. Meanwhile, it is possible to update the timeout of the TCP connection. With the HTTP / 1.1, the server can reuse connections faster apparently.Īprelium will therefore apparently do an update to use HTTP1.1 in reverse proxy. It does not help to reduce the number of TCP connections… So, all requests are doubled.Ī web app, so an application which by nature already generates a lot of requests to the serverĪ Xojo web app, 100% server, which by nature generates more requestsĪ proxy (this may be similar with CGI?) which doubles requestsĪbyss uses HTTP / 1.0 reverse proxy, so each request uses a TCP connection (after, this connection is not used, so it is grayed out in the resource monitor). The proxy then relays the requests to the web app (the loopbacks). There is a request (TCP connexion) for each resource: each image, css, javascript each file, etc. This causes multiple requests to the proxy (Abyss). The app on this server is much more complex.Īpparently, in reverse proxy, each request performed causes a second.Įxample: I display the web app in my browser. It does seem to spike some loopback processes but not so many and the app generally works very well. I have another totally different virtual server in a different datacenter that is a very similar configuration except it uses MySQL. I have a 15 minute timeout and by the time that is reached there are about 25 connections. If I remain on a page in the app the loopback connections start to drop. If I logout and close the browser it settles back to only a few connections and no loopback connections. This is all with no other users in the system. If I go ahead and login to the first main page and do nothing I can see the connections spike to well over 250 and slowly rise to maybe 300 even if I do nothing. I do have a keypress event that looks for the ENTER key for the UserID and PW (the only keypress events in the app). If I type the User ID and tab to the password field the TCP connections spikes to more than 100 then in a minute or so starts to settle back to the 50 level. If I launch the login page and do nothing it seems to create about 50 connections and more than 40 are these loopback connections. The remote port is the same for every one of these TCP loopback connections generally in the 25,000 range. ![]() The local port is listed as a high number port (50,000 range) and all seem to increment by one for each. These show in the resource monitor with no Image Name (program) and no PID (Process ID). When the first connection comes up to the login page the app spikes to at least 50 TCP connections that are mostly these “IPv4 loopback”. If the app is not being accessed (no active browser connections) the TCP connections drops to just a few and none are loopback. It was built with 2014r3.1 but I also tried 2014r2.1 with the same results.Īs I dug into things with Resource Monitor (which can be run from the Performance Tab of the Task Manager in Server) I saw many TCP Connections listed as “IPv4 loopback”. It is so problematical it cannot really be used. The app was sluggish and would simply drop off line from time to time. I added a second Web App and today it began to get some use and it started having problems. ![]() I have had intermittent problems since it has been deployed. I am using the Abyss Webserver and the app is accessed securely (HTTPS). It has 8GB of RAM and 4 virtual processors. I have a Web App that runs on a Windows Server 2008 Standard running in VMWare ESXi.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |