Troubleshooting Websphere can be a pain if you’re unsure where to start. So lets start the mustgather using the below link.
http://www-01.ibm.com/support/docview.wss?uid=swg21141054
In lui of starting the WebSphere Caching Proxy in debug mode, you can
dynamically gather the information using the GUI. I have included the
GUI tracing information:
—————————————————-
To enable and access the admin page from admin port, please first
enable the following directive in the ibmproxy.conf:
AdminPort 8008
After the proxy is started, the admin tracing page could be accessed by:
http://proxyserver:8008/admin-bin/trace
When the problem happens, in the above admin tracing from, please check
“Very Verbose” and select following modules:
format, http, proxy, request, socket, ssl, tcp, time, timer,
persist, connection-pool, proxychain, and proxygroup
Then click “make it so” and allow proxy run for another 10 minutes.
Lastly, send us all the logs the proxy generated as well as the
ibmproxy.conf file.
By default, the admin page is password protected, to add an admin user,
please run following command:
htadm -adduser webadmin.passwd user-id password
under /opt/ibm/edge/cp/server_root/protect folder. Or disable the
following Protect directive in the ibmproxy.conf by un-commenting:
#Protect /admin-bin/* PROT-ADMIN
————————————————
Also, it would be helpful to get IP traces done on the WCP and IBM HTTP
Server (IHS) at the same time. Two sets, one working and one failing
would be helpful. I have included a technote on IP tracing: