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.
Then we get a series of 40 - 50 of the following message over a period of a couple of hours or so (the difference being in the additional ntdll! lines at the top of the message which varies from 2 - 4 aditional lines):
Beginning with the first message above, the number of concurrent users on the web server starts a sharp and steady climb until eventually it hits around 140 - 270 concurrent users.
At this point the web server disappears from the network - we cannot get pages through HTTP, we cannot ping it or FTP to it.
If we stop and restart the World Wide Web Publishing service everything returns to normal and the number of concurrent users drops straight down to the normal 25 - 45 and stays there. We get no more of the messages shown above until the next time this cycle repeats.
On our web server we have installed the WebFocus cgi piece that allows us to interact with a WebFocus application server on a separate server.
On the web server we also have ColdFusion 5.0.
Does anyone have ideas on what might be going on here?
Why are we getting these webapi/webcgi errors?
Is the source of these errors a WebFocus problem that is ultimately causing the WWW Publishing service to fail or are the messages the symptom of another problem?
George, all i can offer is that, like you, we run iis5, wn2ka server, and always use isapi for our selfserv wf site and servlet for our Caster activities and our mre development activities. and we've never had this problem,in any version from 436 up to 525. But we do have a dedicated box, nothing else runs on it. We run webfocus in security protected mode, not as a service, and on reboot we always have to start caster manually. Are you running as a service?
Posts: 3811 | Location: Manhattan | Registered: October 28, 2003
I have also been following this problem at SSA for a while now. The WebFOCUS software involved is release 4.3.1. We are running this as a service. This problem is also evident in our Chicago regional office with their WebFOCUS setup. Chicago has upgraded to 5.2.5 and this did not solve the CGI issue. They are now looking to move to servlets.
George, Unfortunately, the likely scenario is that the isapi.dll is bringing down your webserver. It is important to know the release, since there were various memory leaks fixed using isapi after 431. ibiweb.exe would most likely not have this problem, since it is not as tightly integrated with the web server. Lets see which version your using.
Regards, Ben Naphtali Strategic Support Manager Business Intelligence Products Group
Posts: 34 | Location: 2 Penn Plaza | Registered: July 29, 2004
We originally deployed our apps using ibiweb.exe but we were forced to use isapi (webapi.dll) because our webmaster could not get the permissions correct with IWA to use ibiweb.exe. This occured after a Windows server upgrade and one of our major apps was rendered inaccessable due to permissions on the file ibiweb.exe so we switched to isapi access which worked.
A second app has always used ibiweb.exe but it is not under IWA security. Maybe you are on to something.
Lou, I expected all of the isapi memory problems to be addressed in the release your running. If you need something running TODAY, then you can use ibiweb.exe which is process based. If there is some sort of failure in one of the connections, there is much less chance that it will affect the WebServer, and it will also work with IWA. The benefit and tradeoff of using ibiweb.exe is that it is process based. The processes are better isolated, but you have the potential to lose some performance. You should also be aware that IIS provides some protection like this as well. Depending on the version of IIS, there are different settings. IIS 5.0 provides 3 levels of Application Protection: low, medium and high. High will run applications outside of the Web Server Service. All of this does not solve the original problem, but lessens the impact. To pursue the original problem, please open a case with Customer Support. If there is some sort of reproduction, that would be helpful. If not, I'm sure we can come up with some additional diagnostics that will pinpoint the problem. Regards, Ben Naphtali Strategic Support Manager Business Intelligence Products Group
Posts: 34 | Location: 2 Penn Plaza | Registered: July 29, 2004