Often times we run into scenarios where we want to see HTTP traffic received by JBoss.
Typical scenarios are when you are debugging SSO problems. You want to see if correct HTTP headers are received by JBoss (LiveCycle User Manager, to be specific).
Tools like Charles Proxy allow you to capture HTTP traffic from the client machine, sometimes installing any new tool on a business user’s machine is not an option.
Enough of context setting.. Main point I wanted to convey was it’s easy to log HTTP traffic on JBoss by following the steps below.
1) Edit – [JBOSS-HOME]/server/deploy/jboss-web.deployer/server.xml
2) Uncomment the following 2 valves for Catalina.
<Valve className=”org.apache.catalina.valves.RequestDumperValve” />
3) Restart JBoss.
Please note that localhost_access_log.log file (new file that gets created) only contains request headers – metadata so to speak. The JBoss server log (server.log) contains actual HTTP requests and responses which you typically need to investigate.