Focal Point Banner


As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.

Join the TIBCO Community
TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.

  • From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
  • Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
  • Request access to the private WebFOCUS User Group (login required) to network with fellow members.

Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.


Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [CLOSED] WFServlet delay in request being processed

Read-Only Read-Only Topic
Go
Search
Notify
Tools
[CLOSED] WFServlet delay in request being processed
 Login/Join
 
Bruce Baum
Member
posted
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,


WebFOCUS 7.7
Windows XP, HTML
 
Posts: 3 | Registered: October 07, 2010Report This Post
dhagen
Virtuoso
posted Hide Post
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?


"There is no limit to what you can achieve ... if you don’t care who gets the credit." Roger Abbott
 
Posts: 1102 | Location: Toronto, Ontario | Registered: May 26, 2004Report This Post
dhagen
Virtuoso
posted Hide Post
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.


"There is no limit to what you can achieve ... if you don’t care who gets the credit." Roger Abbott
 
Posts: 1102 | Location: Toronto, Ontario | Registered: May 26, 2004Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic

Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [CLOSED] WFServlet delay in request being processed

Copyright © 1996-2020 Information Builders