Symptoms
If there is heavy load on iControl SOAP that leads to a large number of opened transactions that never get closed, there is a chance that the iControlPortal.cgi process will crash.
Impact
As the transactions begin to timeout, there is a small chance that the load will cause the portal to crash and return a 500 error.
Conditions
The user opens many transactions in iControl SOAP and puts the portal under heavy load.
Workaround
There is no workaround except not to open many transactions and allowing them to timeout while under heavy load, though the crash is rare.
Fix Information
The iControl SOAP portal no longer crashes under a heavy load with many open transactions.
