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

A quick disclaimer...

Although I put in a great effort into researching all the topics I cover, mistakes can happen. Use of any information from my blog posts should be at own risk and I do not hold any liability towards any information misuse or damages caused by following any of my posts.

All content and opinions expressed on this Blog are my own and do not represent the opinions of my employer (Oracle). Use of any information contained in this blog post/article is subject to this disclaimer.
Hi! You can search my blog here ⤵
NOTE: (2022) This Blog is no longer maintained and I will not be answering any emails or comments.

I am now focusing on Atari Gamer.