Our team is experiencing some significant delay when requesting to execute a .fex from a page of URL links. We captured the behavior using HttpWatch.

In some cases, a POST is made to WFServlet, with no parameters, and a delay of anywhere from 8-30 seconds results.

Until WFServlet processes the POST, the HTML can not execute to start its logic (which includes launching queries to retrieve data to populate a variety of SELECT / filter boxes).

For other reports, WFServlet is activated via a GET with parameters, and there is essentially no delay.

Can anyone provide a hint on what causes a difference between the POST and GET operation, and the wait time behavior?

This message has been edited. Last edited by: Kerry,

Wow! What application server are you using? Is it configured for HTTP 1.1 or 1.0?

The biggest difference is how your network adapters handle the request. A POST is defined as non-caching, while GET can be cached on any smart network device along the request. POST will get a lot more scrutiny along the way and can be perceived as requesting changes at the target. GET is more passive and is seen as a request for something from the target.

What is the time delay if you make the request on the same server as the install and use localhost or 127.0.0.1 to keep the network layer from engaging?

I know the timing of this is really weird, but I was at a customer yesterday afternoon that was suffering from the same problem. When they logged onto dashboard, it would take anywhere from 25-35 seconds just for the screen to render without any reports being called. They were using Tomcat 6.02 and the HTTP listener was was defined with protocol="HTTP/1.1". I removed the protocol attribute and restarted tomcat. After that, the dashboard logon was almost instantaneous.