Troubleshooting
Problem
Collecting data for problems with the IBM WebSphere Application Server proxy server (WebSphere proxy server). Gathering this information before calling IBM support will help familiarize you with the troubleshooting process and save you time.
Resolving The Problem
If you have already contacted support, continue on to the component-specific MustGather information. Otherwise, click: MustGather: Read first for WebSphere Application Server.
General proxy troubleshooting
| Problem | Possible solution |
| Config/rule/action not getting applied | Make sure virtual host, rule, and action are all “enabled” in the console. |
| Proxy will not start | Make sure no other processes are listening on the ports the proxy binds to (for example, 80 and 443). |
| Request does not succeed | Update the virtual host to add the proxy’s http and https listening ports (default 80 and 443 are already in default_host) Try hitting the application directly on the Web container port. If you cannot do this, the proxy will not be able to hit it either. |
If the previous suggestions fail to resolve your problem, then enable the proxy tracing.
- Clear all WebSphere proxy server logs:
native_stderr
native_stdout
SystemErr
SystemOut
trace*.log
cache*.log
local*.log
proxy*.log
The log files are located in the following directory:
profile_root/logs/server_name
Note: If you have configured to write WebSphere proxy server log files into a different location, then clear them accordingly.
- Clear all WebSphere proxy server FFDC logs. FFDC files are located in the following directory:
profile_root/logs/ffdc
Note: If you have configured to write FFDC log files into a different location, then clear them accordingly.
- Enable and collect WebSphere proxy server traces with the following trace string: (All should be in one line. Line breaks were added in this technote to help readability.)
com.ibm.ws.proxy.*=all:
com.ibm.ws.odc.*=all:
com.ibm.ws.dwlm.*=all:
WLM*=all:
HTTPChannel=all:
GenericBNF=all
- If the problem takes time to recreate then you may want to consider modifying the Diagnostic Trace Service settings of the WebSphere proxy server to specify a larger Maximum File Size and Maximum Number of Historical Files. A trace file size of 50M and number of historical files 20 is usually sufficient. This setting can be discussed with your IBM support representative.
Proxy server MustGather information
Recreate the problem and collect the following documents to send to IBM:
- native_stderr
- native_stdout
- SystemErr
- SystemOut
- trace*.log
- cache*.log
- local*.log
- proxy*.log
Above files are in profile_root/logs/server_name
- target.xml (this will appear once odc trace is enabled) from the following directory:
profile_root/installedFilters/WLM/proxy_name
- FFDC logs with the current date, located in the following directory:
profile_root/logs/ffdc
- All of the files located under the Proxy profile config folder:
profile_root/config/cells/cell_name/nodes/node_name/servers/server_name
- All of the files located under the Proxy profile_root/installedFilters folder.
Follow these instructions to send diagnostic information to IBM support.
Related Information
[{"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Proxy server","Platform":[{"code":"PF033","label":"Windows"}],"Version":"9.0.0.0;8.5;8.0;7.0","Edition":"Network Deployment","Line of Business":{"code":"LOB45","label":"Automation"}}]
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21389667