Two solutions for OGG Directorwebhang
There are two solutions for OGG Director web hang:
Description of Director web hang of OGG: It indicates that the web interface can be logged in, but the refresh date is a long time ago and does not change.
One of the situations where the Director web hang of OGG lives:
Purpose
OGG Director web displaying "Error 500-Internal Server Error" in the event log window. this issue can also result in successful login to Director web but monitored hosts are shown in red. the domain. log in
\ Domain \ servers \
\ Logs shows: <Mar 4, 2011 10:24:10 pm cst>
Troubleshooting Steps
OGG Director server uses WebLogic to host the Director application. Inside the WebLogic domain, WebLogic creates a file based paging store. When weblogic jvm runs low on memory, this is used to page non-persistent messages. Usually, the place is:< weblogic_install>\user_projects\domains\$DomainName\servers\$ServerName\tmp So, for Director environment, it would be< Director_Server_installLocation>\domain\servers\
\tmp e.g.
\domain\servers\localhost\tmp The suggested solution is:-1. stop the Director server 2. Take a backup of "tmp" directory:< Dir-server-install>\domains\$DomainName\servers\$ServerName\tmp 3. Delete the tmp directory under< Dir-server-install>\domains\$DomainName\servers\$ServerName\tmp 4. Restart the Director server The tmp directory will automatically be created again when WebLogic needs to cache messages.
Case 2 of OGG ctor web hang:
That is, the tables ACONPROCSB, STATSENTRYB, LOGENTRYB and all JMS _ * tables are too large. Make a scheduled task truncate.