[CLOSED] Can a FOC198 Error Make UI Unresponsive?

Hi -

We are running Apache Tomcat standalone on a Windows 2003 Server SP2 with WebFOCUS Server 7.6.10.
Recently we had a drive space issue which I believe was the cause of some FOC198 errors. It is also possible we exceeded the 2Gig limit for the FOCSORT.
Be that as it may, the user interface (BI Dashboard) became unresponsive at approximately the same time as the FOC198 error. We couldn't even bring up the login screen or the ibi_apps page.
I restarted the services and all seems to be OK for now. I've searched the log files for Tomcat and EDAPRINT and I've looked through the server's event log and, other than the FOC198 issue, I don't see anything that might indicate why the system stopped responding.
I someone here confirms that a FOC198 error can cause the system to hang I'll quit pulling my hair out trying to locate the source of the hang. Otherwise, can you tell me where else I might look to determine what's may have happened?

Thanks!

Dan

This message has been edited. Last edited by: Dan Pinault,

7.7.05M/7.7.03 HF6 on Windows Server 2003 SP2 output to whatever is required.

Posts: 393 | Location: St. Paul, MN | Registered: November 06, 2007

GamP

Virtuoso

posted

Hide Post

Dan,

The dashboard and/or MRE user interface do not use any focus database. All they need are plain text files (htm, xml, css, jsp) and some images. What may have been the case is that because of the drive space problems you mentioned, the app server (tomcat in this case) could not write whatever it needed to write to disk. Also logging this could not be done because of the disk space problems. So there was no way left to notify the user what was happening and the system just froze.

Since there is no way to confirm this, it is just a guess, I may be way off the mark...

GamP

- Using AS 8.2.01 on Windows 10 - IE11.
	in Focus since 1988

Posts: 1961 | Location: Netherlands | Registered: September 25, 2007

Ignored post by GamP posted

Show Post

<JG>

posted

If general space was an issue then an unresponsive UI is a distinct possibility.
Even though Dashboard/MRE is not using Focus DBs it still requires work space on the server
for processing, caching etc.

GamP is quite correct with regards logging, No space = no log.

The FOC198 is generally related to either
1. exceeding the size limit for a FOCUS db OR
2. because the FOCUS DB is corrupt preventing read/write operations OR
3. because of general space limitations the DB cannot be expanded to add additional pages as required.

Based on the fact that space was an issue I would tend to suspect 3. and 1. in that order

Dr. Nick

Gold member

posted

Hide Post

Hi Dan,
Received FOC198 in a variety of situations: 1. when FOCUS DB has a pointer error; 2. when user triggers Maintain case then closing with javascript self.close(); The first situation is usually caused by a Maintain and Modify executing against a FOCUS DB at the same time where both are adding new instances. For this situation you must rebuild FOCUS DB while application is offline.

The second situation is usually a local error where the user must first close all browser windows then open a browser window and restart the application. Here you must remove the activity that proceeds the self.close().

I've received FOC198 at other times but have not been able to accurately identify the situations.

Hope this helps,
Nick

WebFOCUS 7.7.03 & 8.0.7
Windows
HTML, Excel, PDF, etc.
Also, using Maintain, etc.

Posts: 83 | Registered: February 26, 2009

Ignored post by Dr. Nick posted

Show Post

Dan Pinault

Guru

posted

Hide Post

Thanks everybody. We haven't had any 'hangs' since we cleaned up the disk space issue.

Keeping my fingers crossed