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.
Actually, it's from tomcat being restarted, and once it's off, this appears, and rightfully so. However, about the "max agents" or even "max processes" or "max load", is there a more succinct way of remedying this situation rather then "restarting tomcat"? I'm thinking along the lines of concentrating on ending that/those processes instead of restarting tomcat all the time.
This would be similar to the difference of doing an “End Process” or “End Process Tree” from within Task Manager instead of restating your computer. While restarting your computer does, in fact, eliminate the issue, It’s like using a canon to kill a butterfly.
So, the bottom line is: is there a better way to remedy this offending issue?
Posts: 3132 | Location: Tennessee, Nashville area | Registered: February 23, 2005