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     tscom3 memory alloc high even when idle

Read-Only Read-Only Topic
Go
Search
Notify
Tools
tscom3 memory alloc high even when idle
 Login/Join
 
dballest
Platinum Member
posted
We have a number of available agents and when we first start them, the memory allocation is about 7004K per tscom3. When we run a report, the tscom3 jumps to 34567K. Even after the report is done and the agent is idle, the memory allocation does not go back to pre-execution size (7004K). What's worst is that we have a tscom3 with a size of 1053467K and no report is running.

Is there a way to automatically reset the allocation?

Thanks,
Dan


Dev: WebFOCUS 7.6.10, Data Migrator 7.6.10
QA: WebFOCUS 7.6.10, Data Migrator 7.6.10
Prod: WebFOCUS 7.6.2, Data Migrator 7.6.8
Windows 2K3, Tomcat 5.5.17, IIS 6
Usage: HTML, PDF, Excel, Self-serve, BID and MRE
 
Posts: 197 | Location: Roseville, CA | Registered: January 24, 2005Report This Post
hammo1j
Master
posted Hide Post
In workspace configuration - Data Services and the set of Agents you use there is idle limits etc etc to mess around with.

Be aware that the whole point of agents is to provide a swift response by having the resources on standby. You will have to make compromises (as always in this life!)


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, 2006Report This Post
dballest
Platinum Member
posted Hide Post
hammo1j,

Thanks for the reply.

Having 50 or even 100 agents on standy is not really a problem for us. The problem is when an agent is running and the memory allocated to that agent builds up to 104MB and not release it after it becomes idle again.

If for example we start with 50 agents and we set the memory limit to 150MB and it goes over, the workforce manager will kill that agent. We will be then have 1 less agent in stand-by. The Workspace Manager will not attempt to maintain the number of agents (from number_ready) after startup if agents are terminated for any reason.

We don't really want to terminate the agent. We want it to de-allocate the memory when it goes back to the idle state.


Dev: WebFOCUS 7.6.10, Data Migrator 7.6.10
QA: WebFOCUS 7.6.10, Data Migrator 7.6.10
Prod: WebFOCUS 7.6.2, Data Migrator 7.6.8
Windows 2K3, Tomcat 5.5.17, IIS 6
Usage: HTML, PDF, Excel, Self-serve, BID and MRE
 
Posts: 197 | Location: Roseville, CA | Registered: January 24, 2005Report This Post
Darin Lee
Virtuoso
posted Hide Post
might just try shortening the idle agent limit. Small overhead because it may have to start a new agent, but any resources the agent controls (such as memory) are released when the agent is shut down after x seconds of "idleness" - a compromise as earlier suggested with a minimal overhead/delay if the agent stays idle for too long


Regards,

Darin


In FOCUS since 1991
WF Server: 7.7.04 on Linux and Z/OS, ReportCaster, Self-Service, MRE, Java, Flex
Data: DB2/UDB, Adabas, SQL Server Output: HTML,PDF,EXL2K/07, PS, AHTML, Flex
WF Client: 77 on Linux w/Tomcat
 
Posts: 2298 | Location: Salt Lake City, Utah | Registered: February 02, 2007Report This Post
newtofocus
Platinum Member
posted Hide Post
Use the agent refresh limit option. That way you can assure that the agent is refreshed and also standing by so that it does not have to started when the request comes.


WF7.1.4 Prod/Test, MRE, self serve, DM
 
Posts: 176 | Location: Desplaines | Registered: August 05, 2004Report This Post
Darin Lee
Virtuoso
posted Hide Post
this would do basically the same thing. with one correction - agent refresh doesn't start a new agent. it just stops the old one after x number of connections. so is isn't standing by - it also has to start a new agent when requested


Regards,

Darin


In FOCUS since 1991
WF Server: 7.7.04 on Linux and Z/OS, ReportCaster, Self-Service, MRE, Java, Flex
Data: DB2/UDB, Adabas, SQL Server Output: HTML,PDF,EXL2K/07, PS, AHTML, Flex
WF Client: 77 on Linux w/Tomcat
 
Posts: 2298 | Location: Salt Lake City, Utah | Registered: February 02, 2007Report This Post
dballest
Platinum Member
posted Hide Post
Thanks for the replies.

Darin,
If for example you got like 3 agents active and all of them are used most of the time and the idle limit value (say 1 hour) does not get triggerred, the agent memory allocation continues to grow. The manager will not get a chance to kill it and restart one (with a much lower memory allocation), unless of course you manually terminate it.


Dev: WebFOCUS 7.6.10, Data Migrator 7.6.10
QA: WebFOCUS 7.6.10, Data Migrator 7.6.10
Prod: WebFOCUS 7.6.2, Data Migrator 7.6.8
Windows 2K3, Tomcat 5.5.17, IIS 6
Usage: HTML, PDF, Excel, Self-serve, BID and MRE
 
Posts: 197 | Location: Roseville, CA | Registered: January 24, 2005Report This Post
Darin Lee
Virtuoso
posted Hide Post
They ALL eventually get recycled due to agent refresh, but i think the default value is 100. Shorten that limit (along with idle limit) and you get something more useful


Regards,

Darin


In FOCUS since 1991
WF Server: 7.7.04 on Linux and Z/OS, ReportCaster, Self-Service, MRE, Java, Flex
Data: DB2/UDB, Adabas, SQL Server Output: HTML,PDF,EXL2K/07, PS, AHTML, Flex
WF Client: 77 on Linux w/Tomcat
 
Posts: 2298 | Location: Salt Lake City, Utah | Registered: February 02, 2007Report This Post
dballest
Platinum Member
posted Hide Post
Darin,

That's exactly what I did in our QA environment. I cut it in half and notice the memory hovers at a lower level than before.

Thanks.


Dev: WebFOCUS 7.6.10, Data Migrator 7.6.10
QA: WebFOCUS 7.6.10, Data Migrator 7.6.10
Prod: WebFOCUS 7.6.2, Data Migrator 7.6.8
Windows 2K3, Tomcat 5.5.17, IIS 6
Usage: HTML, PDF, Excel, Self-serve, BID and MRE
 
Posts: 197 | Location: Roseville, CA | Registered: January 24, 2005Report 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     tscom3 memory alloc high even when idle

Copyright © 1996-2020 Information Builders