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.
Has anyone experienced this error when trying to access the Reporting Server Console (EDASERVE) " No free agents available on the server to process the request at this time. Try again later."
We checked the agents currently running and there were only about 15 running..
Thank you.This message has been edited. Last edited by: Joey Sandoval,
Prod/Dev: WebFOCUS 8.0.08 on Windows Server 2008/Tomcat , WebFOCUS DevStudio 8.0.08 on Windows 7 Pro
I have encountered this issue with 8001 server, Restarting the WFRS resolved this issue, Also setting agent_refresh=100 made this issue to occur rarely. I would recommend you to open a case with IBI tech support (you could reference our case which describes similar symptoms 82992509 )
Thanks ABT. So Did you end up setting the agent_refresh parameter to equal 1 on all data services or just WC_DEFAULT?
I created a case with IBI and they also suggested changing the Maximum value from 2 to 5 or more, depending on how many users we have connecting to the web console.
Prod/Dev: WebFOCUS 8.0.08 on Windows Server 2008/Tomcat , WebFOCUS DevStudio 8.0.08 on Windows 7 Pro
Originally posted by Joey Sandoval: Thanks ABT. So Did you end up setting the agent_refresh parameter to equal 1 on all data services or just WC_DEFAULT?
I created a case with IBI and they also suggested changing the Maximum value from 2 to 5 or more, depending on how many users we have connecting to the web console.
Here's my current EDASERVE.cfg (appropriate sections):
crashed_cleanup = on
SERVICE = DEFAULT
BEGIN
maximum = 50
number_ready = 2
agent_refresh = 1
maximum_q = 10
END
SERVICE = WC_DEFAULT
BEGIN
maximum = 2
number_ready = 2
maximum_q = 20
agent_refresh = 1
END
SERVICE = DFM_DEFAULT
BEGIN
maximum = 10
number_ready = 0
agent_refresh = 1
maximum_q = 10
END
I may not have done everything "the smart way", but its effective. ;-)
IBI has informed me that updating agent_refresh is no longer necessary on our release. However, I did update the max and number_ready values to 5 as recommended. Thank you all for your input.
Prod/Dev: WebFOCUS 8.0.08 on Windows Server 2008/Tomcat , WebFOCUS DevStudio 8.0.08 on Windows 7 Pro