NOTE: This article is 3 years or older so its information may no longer be relevant. Read on at your own discretion! Comments for this article have automatically been locked, refer to the FAQ
for more details.
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:
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.
A quick disclaimer...
Although I put in a great effort into researching all the topics I cover, mistakes can happen.
If you spot something out of place, please do let me know.
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
Other posts you may like...