Switch / NIC Auto Sensing Can Cause ColdFusion Server to Hang

It was interesting to see a recent post on Joel Spolsky's blog explaining that a recent service outage in their hosting environment was caused by accidentally setting their switch to auto-sense network speed. In the post, he acknowledges that they do normally set the network speeds manually and turn off autonegotiate but that one switch had slipped through the cracks.

Leaving autonegotiate turned on can cause all sorts of sticky problems on a network because during negotiation a switch can drop packets. In an office network this is less noticeable, but in a high load environment it can really toss a wrench into the works.

In fact, as reflected in this post on the short lived CF-Guru blog you can see that this same setting can cause CF to potentially hang and depending on load, eventually fail.

So consider this a friendly reminder. In production environments, peg all the switches and NICs to a set speed.

Comments (2)

Add Comment ]

David Sirr I can second that opinion, we had servers hanging after a recent move to a new datacentre... after much frustration it turned out to be the NIC auto sensing.
Charlie Arehart For folks reading this, if you want to see that old cfguru.org blog entry that Cameron points to, while the link offered breaks, you can find it with the good ol' wayback machine: http://web.archive.org/web/20070126122711/www.cfguru.org/index.cfm/2006/6/6/Network-Auto-Sensing-Causes-ColdFusion-Server-to-Hang

Some good additional stuff in there.

Add Comment ]

Post a comment





Leave this field empty: