MustGather: Edge Caching Proxy
 Technote (FAQ)
 
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
  1. 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


  2. 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


  3. Tracing for request not proxied correctly:
    1. To enable tracing at proxy startup from the command line:
      1. Define a TraceLog <filename> in the ibmproxy.conf file under Logging Directives.
      2. Start your proxy in debug mode with the command:

        ibmproxy -debug -mtv

      3. Information will be written to the trace file and to the console. This is normal.
    2. To enable tracing during runtime:
      1. Go to http://<proxyname>:<port>/Usage/Frames.
      2. Click on the Rtrace link.
      3. Define the TraceFile name, select the verbosity level, and click Submit.
    3. After starting the trace:
      1. Recreate your problem.
      2. Stop the trace by pressing <Ctrl>-C.
        Caching Proxy trace logs do not wrap. They are limited to 2 GB in size.

  4. Logs to collect (purge existing logs first):
    • CacheAccessLog
    :cache hits
    • ProxyAccessLog
    :proxied requests
    • Access log
    :requests serviced locally
    • ErrorLog
    :configuration errors and request errors
    • EventLog
    :informational events during runtime
    • stderr
    :stderr is redirected to file
    • stdout
    :stdout is redirected to file


  5. 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


  6. 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.
 
Related information
Submitting information to IBM support
Steps to getting support
MustGather: Read first
Troubleshooting guide
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers WebSphere Application Server Edge Component 6.0
 
 


Document Information


Product categories: Software > Application Servers > Edge Servers > WebSphere Edge Server > Caching Proxy
Operating system(s): Windows
Software version: Edge Server 2.0.x
Software edition:
Reference #: 1141054
IBM Group: Software Group
Modified date: Mar 2, 2005