|
Problem |
MustGather for problems with the WebSphere® Application
Server Edge component, Caching Proxy. Gathering this information before
calling IBM support will help familiarize you with the troubleshooting
process and save you time. |
|
Solution |
If you have already contacted support, continue on to the
component-specific MustGather information. Otherwise, click: MustGather:
Read first for all WebSphere Application Server products.
Caching Proxy specific MustGather information
- Version of Caching Proxy installed:
For AIX®:
|
lslpp -l | grep wses |
Where "wses" is lowercase.
|
For Solaris™:
|
pkginfo | grep WSES
pkginfo -l WSEScp.# |
Where # is the highest number (for example, 1, 2, 3, and so on) and
"WSES" is uppercase.
|
For Linux®:
|
rpm -qa | grep WSES |
Where "WSES" is uppercase
|
For Windows®:
Go to the Registry, then:
|
HKEY_LOCAL_MACHINE\SOFTWARE\IBM\WSES-Caching
Proxy\CurrentVersion |
|
- The ibmproxy.conf file located in the following directory:
For UNIX® or Linux:
|
/opt/ibm/edge/cp/etc/en_US |
For Windows:
|
C:\Program
Files\IBM\edge\cp\etc\en_US |
|
- Tracing for request not proxied correctly:
- To enable tracing at proxy startup from the command line:
- Define a TraceLog <filename> in the ibmproxy.conf file
under Logging Directives.
- Start your proxy in debug mode with the command:
- Information will be written to the trace file and to the console. This
is normal.
- To enable tracing during runtime:
- Go to
http://<proxyname>:<port>/Usage/Frames.
- Click on the Rtrace link.
- Define the TraceFile name, select the verbosity level,
and click Submit.
- After starting the trace:
- Recreate your problem.
- Stop the trace by pressing <Ctrl>-C.
Caching Proxy trace logs do not wrap. They are limited to 2 GB in size.
- Logs to collect (purge existing logs first):
|
:cache hits |
|
:proxied requests |
|
:requests serviced locally |
|
:configuration errors and request
errors |
|
:informational events during runtime |
|
:stderr is redirected to file |
|
:stdout is redirected to file |
|
 |
- If Non-SSL, a packet trace might be required.
For AIX®:
|
iptrace -a -b <tracefile
name> |
Format using:
|
ipreport -n <tracefile name>
> trace.out |
|
For Solaris™:
|
snoop -d <interface> -ta -S
>> <text output file> |
|
For Linux®:
|
tcpdump -i <interface> -w
<output file> |
|
For Windows®:
|
netmon OR ethereal packet
trace |
|
- Follow instructions to send
diagnostic information to IBM support.
For a listing of all technotes, downloads, and educational materials
specific to the Edge component, Caching Proxy, search the WebSphere
Application Server support site or the WebSphere
Edge Server support site. |
|
|