Tracing HTTP headers in BusinessWorks 6.5.1
Article ID: KB0077700
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix BusinessWorks | 6.5.1 |
Description
Knowing HTTP Headers arriving at the HTTP Connector may help troubleshoot various interoperability issues.
Issue/Introduction
Resolution
A new feature in Jetty 9.4 (bundled with 6.5.1) makes it easier by enabling the logger org.eclipse.jetty.server.HttpChannel to DEBUG in applicable logback.xml :
<logger name="org.eclipse.jetty.server.HttpChannel">
<level value="DEBUG"/>
</logger>
Headers of each HTTP request will be logged as below:
2019-05-06 12:38:26.020 DEBUG [bwResourceHTTPConnector.qtp-94] org.eclipse.jetty.server.HttpChannel - REQUEST for //localhost:11006/SOAPServiceBinding/getBooksByAuthor/ on HttpChannelOverHttp@9a96fbf{r=1,c=false,a=IDLE,uri=//localhost:11006/SOAPServiceBinding/getBooksByAuthor/}
POST //localhost:11006/SOAPServiceBinding/getBooksByAuthor/ HTTP/1.1
Content-Type: text/xml; charset=UTF-8
SOAPAction: "GetBooks"
User-Agent: Axis2
Host: localhost:11006
Content-Length: 30
Feedback
