One scenario that you may see is the current TIM memory utilization growing up to 80 GBytes and the system becomes unresponsive requiring a restart.
So sometimes arises the need to limit the Flex parser memory consumption in the TIM.
Do note that it is not recommended to use Flex Plugin with high traffic such as found in Production Environments.
If the traffic hits 100% sometimes, then reduce the traffic using web server filters.
The main parameters that limit the Flex plugin are (To be set in the TIM Settings UI):
A value of 1 enables the Flex processing capability, 0 disables it.
Note that FlexPlugin/Enabled must be set to 1 for any of the three settings below to work.
FlexAMFParser - Flex Binary Message Processing
FlexAMFXParse- Flex XML Message Processing
FlexAMFResponseParsingForChunkedTypeEnabled For Streaming Media, AMF data is encapsulated in a chunk which has a header which defines things such as the message length and type. See Wikipedia for more details.
Another common issue is the Flex message size.
The Transaction Impact Monitor (TIM) uses the following properties to limit the message payload size when monitoring Flex applications. The message payload maximum request and response size limit is 200,000.
MaxFlexRequestBodySize: 10000 (Maximum: 200000)
MaxFlexResponseBodySize: 10000 (Maximum: 200000)
This limit avoids TIM processing and memory overhead when Flex has large binary payloads.