Verify that the applet host entry in database (egpl_pref_globalsettings table of Active DB) has the correct server IP address, by running the following query: select * from egpl_pref_globalsettings where setting_name = ‘Common.messaging.applethost’

Verify java console output on client side for errors logged in a format similar to JAVA exceptions (see screenshot). Click View -> Java Console on IE.

Troubleshooting Application Server issues

Application not responding due to high CPU utilization or memory consumption

Verify network connectivity between all servers in the cluster using the ping command: ping <servername>

Run netstat –an –p tcp to find local and remote ports that are potentially being used by an another application/process (see port diagram on next slide that shows ports that are required and used by the application).

After stopping application server

Verify through Windows Task Manager that all java, javaw and cmd processes have been terminated.

####<23-Jun-06 22:30:09 BST> <Warning> <WebLogicServer> <EMS00813> <myserver> <CoreHealthMonitor> <kernel identity> <> <000337> <ExecuteThread: '16' for queue: 'default' has been busy for "763" seconds working on the request "Http Request: /partition1/web/controller/platform/common/login/login.jsp", which is more than the configured time (StuckThreadMaxTime) of "600" seconds.>