Users Guide
Troubleshooting Your Application | Troubleshooting
OMNM 6.5.3 User Guide 689
Mini Troubleshooting
Suggested mini-troubleshooting steps for a balky application that is already installed and running:
1
Refresh the browser. If that does not work...
2
Clear the browser’s cache (Firefox in particular loves persistent old pages), then refresh.
When you see a difference between direct access behavior between browsers on two different
machines, delete temporary internet files. In Windows, open control panel, and open Java.
Click the
Settings
button in the
General
panel, and click
Delete Files
. Delete for
Applications
and Applets
and
Trace and log files.
If that does not work...
3
Stop and start the browser. If that does not work...
4
Stop and start the web server
For Windows, to start the web server manager:
oware\synergy\tomcat-
X.X.X\bin\startsynergy.
For Linux.
/etc/init.d/synergy start
or
/etc/init.d/synergy stop
Worth noting: The tray icon for the web server ( ) is “optimistic” about both when the
web server has completely started and completely stopped. You cannot re-start web server
when its Tomcat process still lingers. If you lack patience, kill the (large) Tomcat process then
re-start web server. The smaller one is that tray icon.
If that does not work...
5
Stop and start application server. Command lines for this:
stopappserver
and
startappserver
If that does not work...
6
Delete the contents of the
oware/temp
directory and restart application server. If that does
not work...
7
Reboot the host and re-start the application server, web server and browser.
When troubleshooting (or contacting technical support), you may find pertinent information in
logs located in the following directories:
..\oware\jboss-5.1\server\oware\log
..\oware\temp\soniqmq.log
..\app_setup.log
..\db_setup.log
You can also run
getlogs
from a command line.
NOTE:
If you see errors that say your Linux system has too few threads, make sure you have set the file handles
correctly.
You may see: The "<portlet> is temporarily unavailable" in portlets after install or upgrade.
Workaround: restart the Web server by stopping and re-starting the synergy service. This can be
done from the Windows tray icon by right-clicking on the Web server.