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.
I am having a problem with the auto prompting on my report. Its a large report, about 2000 lines. I keep getting the HTTP 500 error message when I try to run the report. If I take the auto prompting out it runs fine. It seems that auto prompting seems to cause this error after about 1000 lines or so. Does anyone have any suggestions?
An HTTP 500 error has been returned while processing the web components. The application server log contains information on why this error has occurred. Contact your application administrator or your software vendor support center for further assistance.This message has been edited. Last edited by: Kerry,
When Automprompting is triggered, the reporting server composes and returns an Autoprompt page in which the entire request is embedded, so that when the browser responds the WF client will receive the user's parameter values along with a parameter containing a fresh copy of the original request -- in other words, your entire 2000-line fex gets pass back and forth several times amongst WF server, WF client, and the browser. Possibly some line of your code gets corrupted in the process.
Try this: factor out the guts of your 2000-line request as a fex file in an APP folder of the server library, and submit just a stub fex that declares the amper variables (to trigger the autoprompt) followed by a server-side (non-MR) -INCLUDE referencing that fex. See if that stabilizes the execution.
Posts: 1925 | Location: NYC | In FOCUS since 1983 | Registered: January 11, 2005
I changed the thread stack size on the tomcat server to 512 and that fixed it however I don't like straying from the default install because sooner or later that setting will change and things break again.
I thought about breaking the report up, maybe I'll try that next.
We should not HTTP500 though! I would have thought it was the Tomcat POST size limit. It's the only app server we know that ships with a small limit. It should be zero or much higher. (When WF now installs Tomcat, we set it to 0).
Brian Suter VP WebFOCUS Product Development
Posts: 200 | Location: NYC | Registered: January 02, 2007