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.
we've noticed that the tomcat service on our Windows 2003 server uses more and more RAM throughout the day. On a busier day (we've got all of about 8 users right now, most logon for a few minutes a day) we'll see the tomcat process shoot up to around 2 GB of RAM usage, on very very slow day, it stays around 200-400 MB of RAM usage.
Why does this happen? Is it bad coding on my part? does it happen to you folks as well?
Prod: Single Windows 2008 Server running Webfocus 7.7.03 Reporting server Web server IIS6/Tomcat, AS400 DB2 database.
Is there a way of tracking history of Tomcat memory usage? or do you just have to look at the task manager when it is being used the most? I looked at my dev and prod test box and they are both <130MB.
Thanks, Sayed
WF 8.x and 7.7.x Win/UNIX/AS400, MRE/Portal/Self-Service, IIS/Tomcat, WebSphere, IWA, Realmdriver, Active Directory, Oracle, SQLServer, DB2, MySQL, JD Edwards, E-BIZ, SAP BW, R/3, ECC, ESSBASE
Posts: 285 | Location: Texas | Registered: June 27, 2006
We too have had memory issues in the JVM over the years. It first started in WebFocus 5.3 running on an NT system with WebSphere. We found that the JVM steadily increased it's memory footprint over a period of days. We always run our app servers with verbose garbage collection enabled. Using IBM's GCCollector tool it is very obvious that there is a memory leak in the WebFocus code. We worked with IBI at the time but got nowhere. We simply started to cycle the WebSphere app server once a day to recover the lost memory.
Fast forward to 2007. Now we run WebFocus 7.6 in a z/Linux environment with Tomcat. We again started to see the same exact issues with the memory. Again running verboseGC and using GCCollector we observed the memory leak. We notified IBI but never bothered to open an official case or push the issue. We simply setup crontab to cycle the tomcat server once a day.
In both of these cases (WebSphere and Tomcat) we run the JVM with a minimum heap size of 512Meg and a maximum of 1024Meg.