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.
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,
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 ?
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
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.
|Powered by Social Strata|