Maximum Post Size Error - Troubleshooting Guidance

Body

There you are, looking at a drawing and admiring its beauty and think "Gee, I really would like to export that drawing." But when you attempt to export the drawing you get an error indicating the object exceeded the maximum post size leaving you thinking "What the heck does that mean?"

Okay, this may not be exactly how this scenario plays out in your head, but the core of the problem is that you want to export the drawing and you are being met with an error that does not really help you determine how to resolve the problem. My hope is that this blog post will help in that regard.

First and foremost, this is not an error that can be adjusted within TRIRIGA, so the information below should help in your conversations with your IT support staff in helping them to help you resolve this issue.

What is the purpose of the maximum post size?

The purpose of a maximum post size parameter is to limit the impact of a denial of service attack on your webserver.

What can I do if my TRIRIGA application indicates this error to our users?

Various infrastructure layers contain parameters which can limit the size of a post, so resolving the problem must be an iterative process. The most obvious areas to check would be the application and web server layers. Involve your network team to perform a trace when you are attempting to export a drawing that leads to this error. The trace should identify a server in the communication line which is causing the error to be raised. At that point you would address whatever components on that server are being used that restrict the post size. In an environment where the communications may pass through a variety of servers and routers, you may need to rerun this process multiple time to adjust all of the various post size parameters.

To summarize:

A maximum post size error is not an indication of a problem with the TRIRIGA application, but with the setting of a potentially large number of parameters in your network configuration that limit post size. Engaging your network team to trace the communications will help you find the servers that result in the error being thrown. At that point it becomes a job for the administrators of the servers to determine which parameter to adjust to allow the export process to successfully complete.