Over the weekend we bit the bullet and transferred from our 10-year-old system to a VM setup. Yesterday things looked good until the web volume increased in the afternoon. We utilize a cloud web service (Azure).

Now, I'm not super Linux-savvy, so I hope I'll frame this question correctly.

It appears that after Microsoft sends the FIN (which closes the port/session on their end) Linux is holding onto it. Then, as we watch, MS is re-using those ports too frequently which is causing massive resets to occur. They still show as ESTABLISHED.

Our Linux wiz is convinced that we need to address that issue somehow. But, I'm wondering why it would create a problem just because we upgraded. And I'm wondering if there is somewhere in Linux that these port closures can be controlled. They should close as soon as we are notified of MS's port closure.

To add another wrinkle to the mix, we have another port that is running a similar web process and it remains unaffected. It, however is less intensive.

Also, the language we're using on this machine is BBx Pro5 Basic. This might complicate matters further because it's not exactly "web friendly". So, we may be using a rather rudimentary method.

Even though he didn't think it would help, our Linux guy changed the TimeWaits from 60 to 30. I actually thought this might work. Yesterday we didn't have the same problems we had the day before. But, then again, we didn't have the same volume of traffic to contend with.

Is there any reason to think this change might have solved the problem?