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     Agents not releasing JVM Threads. How to clean up or prevent

Read-Only Read-Only Topic
Go
Search
Notify
Tools
Agents not releasing JVM Threads. How to clean up or prevent
 Login/Join
 
Rocky
Gold member
posted
Hi All,
We got the below answer from IBI...
But where do we change the below things...
Please walk me through........

There is no automatic way or facility to kill an agent. But, the following
settings can be used to manage agent processes:

1. cpu_limit = n
Where n represents the number of seconds for each instance before the
parameter takes affect.

This setting, which in the scope of an agent service, defines the amount of
CPU time an agent is allowed to use before being killed by the Workspace
Manager.

2. connection_limit = seconds
Where seconds is the maximum number of seconds for a connection. The
default is an unlimited number of seconds.

This setting limits the time allowed for a connection to the server. If
queuing is enabled, when the limit is reached, the session is removed from
the queue and the active agent is stopped.


WEBFOCUS 7.6.4
Unix
All output
 
Posts: 65 | Registered: October 26, 2009Report This Post
<JG>
posted
Those settings are in the configuration which you manage from the WebFCOUS server console.

You could also set agent refresh to 1 meaning the agent should cleanup after every request
 
Report This Post
GamP
Virtuoso
posted Hide Post
Go to the web console of the server - http://machine:8121 - change machine for your server name and 8121 for the http port the server is listening on. Log on with the administartor credentials (if asked) and navigate to 'Workspace', Configuration. Expand 'Data Services', right mouse DEFAULT and click on Properties.
In the resulting screen you can change the mentioned variables.


GamP
- Using AS 8.2.01 on Windows 10 - IE11.
in Focus since 1988
 
Posts: 1961 | Location: Netherlands | Registered: September 25, 2007Report This Post
Rocky
Gold member
posted Hide Post
Under work space I only see remote server which is not expanding


WEBFOCUS 7.6.4
Unix
All output
 
Posts: 65 | Registered: October 26, 2009Report This Post
N.Selph
Guru
posted Hide Post
You probably do not have a login with full admin privs on this server. You will have to get the aid of the authorized WF Server admin to change these settings.


(Prod: WebFOCUS 7.7.03: Win 2008 & AIX hub/Servlet Mode; sub: AS/400 JDE; mostly Self Serve; DBs: Oracle, JDE, SQLServer; various output formats)
 
Posts: 391 | Location: California | Registered: April 14, 2003Report 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     Agents not releasing JVM Threads. How to clean up or prevent

Copyright © 1996-2020 Information Builders