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     [CLOSED] WF Server Setting CPU Time Limit

Read-Only Read-Only Topic
Go
Search
Notify
Tools
[CLOSED] WF Server Setting CPU Time Limit
 Login/Join
 
Dwayne
Member
posted
Currently the WF 7.6.11 server has a CPU_LIMIT set at 180 seconds. This is in the ibi\srv76\wfs\bin\edaserve.cfg file. This limit is to stop any run away jobs and does work very well. However, a few jobs do need more CPU time. One option is to run them as ‘deferred’. The deferred jobs have a higher CPU_LIMIT of 300 seconds. This also does work very well.

Here is a portion of the edaserve.cfg file;
SERVICE = DEFAULT
BEGIN
maximum = 40
number_ready = 10
profile = PSLOGIN
agent_refresh = 1
cpu_limit = 180
idle_session_limit = 3600
connection_limit = 7200
END

Now the long running job needs to be run in Report Caster and is subject to the 180 seconds limit. So this limit has been increased, but this effects all programs.

Is there a way to increase the CPU_LIMIT for only special execution userids?

Do I need to create a new special ‘service’ with higher limits, but then how do I control who is using or not using that service?

Looking for options, thanks in advance.

This message has been edited. Last edited by: Kerry,


WF 8005 and Tomcat
OS; Windows 64 bit
Adapters; DB2, People Soft, Oracle, MSSQL
Output; Excel, Doc, Tab, PDF, HTML
 
Posts: 5 | Location: Univ of Nebraaska | Registered: May 15, 2003Report This Post
N.Selph
Guru
posted Hide Post
We have created several Report Caster services. Most have the default user id. We have one that requires userid to be input. Perhaps you can use something like that to control who uses it.


(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
Waz
Expert
posted Hide Post
How about having a second configuration with a longer CPU limit, that Report caster uses.


Waz...

Prod:WebFOCUS 7.6.10/8.1.04Upgrade:WebFOCUS 8.2.07OS:LinuxOutputs:HTML, PDF, Excel, PPT
In Focus since 1984
Pity the lost knowledge of an old programmer!

 
Posts: 6347 | Location: 33°49'23.0"S, 151°11'41.0"E | Registered: October 31, 2006Report 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     [CLOSED] WF Server Setting CPU Time Limit

Copyright © 1996-2020 Information Builders