HTTP Channel does not work in Debugger mode of Studio.
Article ID: KB0093276
Updated On:
| Products | Versions |
|---|---|
| TIBCO API Exchange | - |
| Not Applicable | - |
Description
Description:
When invoking the Gateway via HTTP, an HTTP 404 error is seen with no entry in the Gateway log file. It appears that the Tomcat server is not passing the request to BE. Running (instead of debugging) the same EAR file, the BE layer receives the request and we can see normal logging. When starting the GW in the debugger, the following entry is seen in the log file which does not occur when starting on the command line:
When invoking the Gateway via HTTP, an HTTP 404 error is seen with no entry in the Gateway log file. It appears that the Tomcat server is not passing the request to BE. Running (instead of debugging) the same EAR file, the BE layer receives the request and we can see normal logging. When starting the GW in the debugger, the following entry is seen in the log file which does not occur when starting on the command line:
2015 Jan 21 10:49:33:859 GMT -6 localhost Warning [main] - [driver.http] Ignoring mapping for context URI /*
Issue/Introduction
HTTP Channel does not work in Debugger mode of Studio.
Resolution
Set the Java property "-Dbe.engine.channel.pageflow.genericContext.enabled=true" in the Debug Configuration's VM arguments under the Main Tab of the Debugger. This will make requests reach the Gateway in Debugger mode.
Feedback
Yes
No
Powered by
