Igor Kromin |   Consultant. Coder. Blogger. Tinkerer. Gamer.

Recently we've had a need at work to see exactly what requests have been arriving at one of our WebLogic servers, this meant enabling HTTP Transport dumping to a log file. I've done this previously with success, but this time around I've hit a few issues. Some of our web services would cause a request/response dump to the log file, but some would not. After searching for a while, I found how to ensure that all requests/responses are dumped to the managed server log file, here's how.

The trick is in setting every possible combination of system property that could cause the dump to happen. These are:
 JVM start parameters
-Dcom.sun.xml.ws.transport.http.client.HttpTransportPipe.dump=true
-Dcom.sun.xml.ws.transport.http.HttpAdapter.dump=true
-Dcom.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.dump=true
-Dcom.sun.xml.internal.ws.transport.http.HttpAdapter.dump=true


Simply set JAVA_OPTIONS in your setDomainEnv.sh script and restart the managed WebLogic server. This will cause each of the web service requests and responses to be dumped to the managed server log file. Note that if you have binary attachments going across the network, these will also be dumped, along with any of the HTTP headers.



-i

Did you like this post or found it useful? Considering supporting this Blog to keep its web servers running, any amount helps! Thanks!
Have comments or feedback on what I wrote? Please share them below!
comments powered by Disqus
Other posts you may like...