Shawn Bass posted a blog post about his experiences with Secure Gateway 3.1.1. Shawn explains that after some period of time the private bytes in use by the secure gateway service climbs to a point where it stops working.
Another major problem with this memory leak is that even when the service is no longer working as intended the service still listens on port 443, so a load balanced setup will not be able to detect the problem.
Read more on Shawn’s blog here: http://www.shawnbass.com/Blogs/tabid/58/EntryId/164/Beware-of-Secure-Gateway-v3-1-1-it-has-a-major-memory-leak-that-will-take-down-your-WI-SG-environment.aspx
Also if you need to downgrade be aware of the known security vulnerability in 3.1.
Rene Vester




