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]Sanity Check -- Apache Tomcat simply stopping in Single-Sign-On configuration

Read-Only Read-Only Topic
Go
Search
Notify
Tools
[CLOSED]Sanity Check -- Apache Tomcat simply stopping in Single-Sign-On configuration
 Login/Join
 
Virtuoso
posted
I want to just put this out there in case anyone else is bumping into the same problem at the moment. It's just past Second Tuesday, and my Apache Tomcat is suddenly . . . falling offline. The service is still running, but it doesn't respond to portal requests or App Studio.

Windows Server 2016 Standard.
WebFOCUS 8.203M
Apache Tomcat 8.5.32

This is a Single-Sign-On configuration, IIS into Apache. The source code produced (i.e., the blank page's source) when this occurs --

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv="Content-Type" 
content="text/html; charset=windows-1252"></HEAD>
<BODY></BODY></HTML>


Restarting Apache service gets the portal structure back up, but then I get EDASERVE errors, "Reporting Server not running/responding Node=EDASERVE" for each report on the page.

Restarting WebFOCUS 82 Server fixes that.

ReportCaster continues to run without restart.
I-Way continues to run without restart.

My concern is that there was an update pushed out by Microsoft that has hosed Apache. This is the second time in two days I've had my mission-critical portal fall offline with no errors presented in any log.

Just looking to see if anyone else is having this problem, thought two heads might be better than one.

This message has been edited. Last edited by: FP Mod Chuck,



 
Posts: 1012 | Location: At the Mast | Registered: May 17, 2007Report This Post
Expert
posted Hide Post
Haven't seen this, on linux.

But did you check the ibi_apps app is still running in tomcat ?

Seems like either app_apps failed and or reporting server failed.

Another option could be connectivity, whats your setup ? all on one machine or distributed ?


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
Virtuoso
posted Hide Post
John

the tomcat stderr log should have some hint of what happened. it is in the \ibi\tomcat\logs directory.


Thank you for using Focal Point!

Chuck Wolff - Focal Point Moderator
WebFOCUS 7x and 8x, Windows, Linux All output Formats
 
Posts: 2127 | Location: Customer Support | Registered: April 12, 2005Report This Post
Virtuoso
posted Hide Post
Not a lot of evidence coming from the logs. I get a slug of "potential memory leak" errors as it's on its way out, but my local SE says that's a symptom, not a cause.

I've discovered that WebFOCUS Reporting Server service needs to be restarted even when Apache is restarted as part of normal operations. So that's not a relevant part of the problem. I can just add that to the list on my overnight scheduled restart so it's not an issue. The real issue is Apache coasting to a stop for no particular reason.

Thanks for tuning in gents.



 
Posts: 1012 | Location: At the Mast | Registered: May 17, 2007Report 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]Sanity Check -- Apache Tomcat simply stopping in Single-Sign-On configuration

Copyright © 1996-2020 Information Builders