Things to consider before increasing MAC timeout times:
-The MAC is a server side application and requires RAM on the server. This is unlike the rest of the product which is run on the client side.
-If they increase the timeout time, then the amount of RAM required is vastly increased. This memory will not be reallocated until the MAC either times out or is closed. This will effect performance because other applications will have to wait for the RAM to become available.
-If they are using 32-bit web logic, there is a limited amount of RAM that can be allocated.
-On the other hand if they are using 64-bit web logic, the amount of RAM that can be allocated is vastly increased and increasing the timeout time will have less of an impact on performance overall.
-If they do decide to increase the timeout time, then they should monitor memory usage on their server of a recommended minimum of a couple weeks, just to make sure that this change has not negatively impacted CS.
-Timeout times and performance is a balancing act that Ted doesn't necessarily believe we have fully mastered yet, even with the ASP clients.
-When Qualcomm chose to increase their MAC timeout times against our recommendations against the idea, which Ted suggests to do in this case, the overall performance was negatively impacted and they chose to go decrease their timeout times.
-Standard timeout time for ASP clients is: 20 minutes.
-The actual change itself is not difficult, he mentioned that there is a field in an XML file that would need to be changed.

Increasing MAC Timeout Times
1. On the Application server navigate to the following XML file:
2. In this folder you will find an XML file called web.xml. Edit this file and update the 20 field to be the new timeout time. This value is in minutes.
3. Restart the domain for this to take effect.

Please note that this may effect memory usage on the server. The memory usage should be monitored for a week or so to ensure that it does not negatively impact your performance.