HCL Sametime wiki: Sametime Advanced troubleshooting: Troubleshooting WebSphere Application Server issues in Sametime Advanced 8

Troubleshooting WebSphere Application Server issues in Sametime Advanced 8

Added by ~Dana Dwonusonakoi | Edited by ~Denise Ekresaplopoden on July 17, 2011 | Version 19

Actions ▼

Abstract

Abstract

No abstract provided.

Tags: troubleshooting

ShowTable of Contents

HideTable of Contents

1 How to look for CPU heap issues for WAS
2 How to turn on tracing
3 How to turn on Performance Monitoring Infrastructure PMI
4 Adding WebSphere Application Servver as a Windows service
5 Using the WebSphere Application Servver information center

Where to look for errors (SystemOut, SystemErr, ffdc)
Logging/tracing usually found in /WebSphere/AppServer/profiles/profile_name/logs/. See Logging and tracing at the Info Center.

Server logs:

Look in system error logs, found in /WebSphere/AppServer/profiles/profile_name/logs/server1/SystemErr.log
Look in system out logs, found in /WebSphere/AppServer/profiles/profile_name/logs/server1/SystemOut.log

ffdc logs:

Look in ffdc logs, found in /WebSphere/AppServer/profiles/profile_name/logs/ffdc

How to look for CPU heap issues for WAS

To dump the javacore and/or heapdump on WebSphere:

(start the wsadmin console... you'll be prompted for login/pwd credentials...)
cd \ProgramFiles\IBM\WebSphere\AppServer\bin
wsadmin

(setup for the DUMPS... specifying application server to dump...)
wsadmin> set jvm [$AdminControl completeObjectName type=JVM,process=server1,*]

(when ready to dump... execute the following to get a javacore file...)
wsadmin> $AdminControl invoke $jvm dumpThreads

OR

(when ready to dump... execute the following to get a heapdump file...)
wsadmin> $AdminControl invoke $jvm generateHeapDump

javacore/heapdump file will be in the following directory:
\ProgramFiles\IBM\WebSphere\AppServer\profiles\ST_Advanced_Profile

How to monitor CPU for WebSphere Application Servver
See How to monitor CPU for EB.

How to turn on tracing

You can find on the following page Setting a diagnostic trace on a server external link

how to turn on tracing for the following:

How to turn on logging when looking for persistent chat errors
How to turn on logging when looking for vmm/ldap errors
How to turn on logging when looking for skilltap errors

How to turn on logging when looking for db errors:
Choose this detail level com.ibm.workplace.db.persist.

How to turn on tracing for vmm issues
To look for issues with ldap we will need to enabled wmm tracing. In the admin console, turn on tracing for "com.ibm.websphere.wim.=all:com.ibm.ws.wim.=all:com.ibm.wsspi.wim.*=all" at level FINEST. You should then see a trace.log file (where system.out and system.err live) with this tracing inside.

How to turn on Performance Monitoring Infrastructure PMI

Something to read before setting up:

This is a good page for reading on what to monitor when using PMI Monitoring overall system health external link

Setting it up:

In WebSphere ISC Console, go to Monitoring and Tuning - Performance Monitoring Infrastructure (PMI).
Click server1.
Enable either "Basic" monitoring or "Custom".

Basic monitoring should provide us with the 3 things we are interested in:

Number of DB Connections
Number of JMS Connections
Number of HTTP Sessions

If you are going to do "Custom" monitoring, enable the following statistics to get # of DB/JMS/HTTP connections/sessions: JDBC Connection Pools.CreateCount, JCA Connection Pools.CreateCount, Servlet Session Manager.LiveCount.

Once PMI is enabled you can look at the "Current Activity. To do this:

In WebSphere ISC Console, go to Monitoring and Tuning - Performance Monitoring Infrastructure (PMI).
Click Performance Viewer.
Click Current Activity.
Click server1.

From here on you can click on Summary Reports or Performance Modules which is more fine-grained. In Performance Modules, you can select the 3 statistics we are interested in. The picture below shows how to expand the trees and select the appropriate statistics.

Besides looking at Current Activity, you can View Logs. This option should be in the same location as Current Activity. Click View Logs and browse to the Server File where the PMI logs are saved. This location is usually: WAS\AppServer\profiles\AppSrv01\logs\tpv\

Adding WebSphere Application Servver as a Windows service

1. Modify IBM\was\AppServer\profiles\ST_Advanced_Profile\properties\soap.client.props file so you can stop Lotus Sametime Advanced with specifying a user name and passord. For example:

#------------------------------------------------------------------------------

# SOAP Client Security Enablement

# - security enabled status  ( false[default], true  )

#------------------------------------------------------------------------------

com.ibm.SOAP.securityEnabled=true

com.ibm.SOAP.loginUserid=wasadmin

com.ibm.SOAP.loginPassword=mypassword

#------------------------------------------------------------------------------

2. Configure WebSphere Application Servver to start as a service. User ID must have local security rights. Use the following syntax:

WASService.exe -add "service_name"

               -serverName server

               -profilePath server_profile_directory

For example:

D:\IBM\WAS\AppServer\bin\WASService -add "SametimeAdvanced" -serverName server1

   -profilePath "d:\ibm\was\AppServer\profiles\ST_Advanced_Profile"

   -startType automatic

3. Go to Click Start - Control Panel - Double-click Administrative Tools - Double-click Services. You should see IBM WebSphere Application Server V6.1 - node-name. which is the windows service you just created.

Note: To remove the service, type WASService.exe -remove"service_name" from WAS\bin\. See Starting servers automatically external link

for more info.