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.



Read-Only Read-Only Topic
Go
Search
Notify
Tools
Internal Error
 Login/Join
 
<Kalyan>
posted
hello,
We are getting a "Internal error" message while running some very large reports. Typically we found that thiscome when the no of records is around 20000. Is here a reason for this. Some server setting which limits the no of records that can be fetched ?

Thanks in advance
Kalyan.
 
Report This Post
dhagen
Virtuoso
posted Hide Post
The first thing I would check is the memory the application server is allowed to use. When I've seen this in the past, it came down to changing the default configuration of the J2EE app server (New Atlanta, Tomcat, etc.)

Start with the app server logs and go from there.
 
Posts: 1102 | Location: Toronto, Ontario | Registered: May 26, 2004Report This Post
<Kalyan>
posted
Thanks all of you for suggestions. finally seem to have got rid of the problem.
Earlier we were trying to get the report output straight to the browser. For some reason this was failing ( Webserver configuration perhaps !)
We changed this to save the output in the format required to a temp folder and then accessed the html from there. And it worked !!!

-Kalyan
 
Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic


Copyright © 1996-2020 Information Builders