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.
HTTP 500 is an application failure which in wf will be the java servlet WFServlet.
WFServlet processing occurs in 2 phases.
1. It determines whether all amper variables are resolved and re-directs to an amper prompting screen if not.
2. It passes the resolved query to the wf server and then waits to receive the HTML output from the server and then feeds that back as HTML to IIS which in turn passes data back to the browser.
HTTP 500 can occur at both stages.
Enter the wf administration console > diagnostics > traces > wf servlet > Trace on
Run your proc and refresh the screen - you should see output namely java trace backs which you may need to edit independently of the wf default editor in webfocus71\logs.
This should determine if its phase 1 or 2 or give you some pointers.
Server: WF 7.6.2 ( BID/Rcaster) Platform: W2003Server/IIS6/Tomcat/SQL Server repository Adapters: SQL Server 2000/Oracle 9.2 Desktop: Dev Studio 765/XP/Office 2003 Applications: IFS/Jobscope/Maximo
Posts: 888 | Location: Airstrip One | Registered: October 06, 2006
hammo1j is correct! The output log usually contains the full exception that generated the 500 error.
What I do to make this simple, is I remove the 500 error redirect in the web.xml in my development environments. Now, when I get a 500 type error, I get the full output log dump to my browser. I just find it a pain to in the butt to continually have to find then open the app server logs.
"There is no limit to what you can achieve ... if you don’t care who gets the credit." Roger Abbott
I assume the file is: Drive:\ibi\WebFOCUS53\webapps\webfocus53\WEB-INF\web.xml
And the change to make is:
Before
<!-- Redirect all responses with status code=500 to this page -->
<error-page>
<error-code>500</error-code>
<location>/applicationErrorPage.jsp</location>
</error-page>
After
<!-- Redirect all responses with status code=500 to this page -->
<!--
<error-page>
<error-code>500</error-code>
<location>/applicationErrorPage.jsp</location>
</error-page>
-->
Francis
Give me code, or give me retirement. In FOCUS since 1991
Production: WF 7.7.05M, Dev Studio, BID, MRE, WebSphere, DB2 / Test: WF 8.1.05M, App Studio, BI Portal, Report Caster, jQuery, HighCharts, Apache Tomcat, MS SQL Server
Does anyone know good initial/maximum/thread stack settings and roughly what they mean?
I have further found out Amper autoprompting causes HTP500 errors
1. In proportion to the number of statements containing amper variables (NB not according to the numbers being prompted for) 2. Is less likely to occur if the proc is executed rather than an adhoc fex eg run from within editor of dev studio.
Server: WF 7.6.2 ( BID/Rcaster) Platform: W2003Server/IIS6/Tomcat/SQL Server repository Adapters: SQL Server 2000/Oracle 9.2 Desktop: Dev Studio 765/XP/Office 2003 Applications: IFS/Jobscope/Maximo
Posts: 888 | Location: Airstrip One | Registered: October 06, 2006
We just started getting them last week on a very large program that should be displaying the autoprompt screen when run from Dev. Studio.
Program works fine when run from a browser with a custom launch page.
After 3 hours of cutting and pasting, I traced it down to lines that had tick marks (single quotes) in them. When I removed the lines (commenting them out didn't help) even though lines above them in the fex had the same code, the autoprompt screen appeared. Very strange.