(→Problem) |
(Update with the copy of version: 8.5.2DRAFT) |
||
| Line 1: | Line 1: | ||
=Troubleshooting= | =Troubleshooting= | ||
__TOC__ | __TOC__ | ||
| − | This page provides solutions to common problems in | + | This page provides solutions to common problems in Web Services. |
| − | The following log for | + | The following log for Web Services is saved to the <tt>/var/log/jetty</tt> directory on the Web Services node: |
| − | *<tt>cloud.log</tt> — Stores WARN level messages about | + | *<tt>cloud.log</tt> — Stores WARN level messages about Web Services. |
<!--*<tt>recording.log</tt> — Stores INFO level messages for call recording.--> | <!--*<tt>recording.log</tt> — Stores INFO level messages for call recording.--> | ||
To modify the log message levels, you can edit the <tt>$JETTY_HOME/resources/logback.xml</tt> file and change the level to DEBUG or TRACE (instead of WARN): | To modify the log message levels, you can edit the <tt>$JETTY_HOME/resources/logback.xml</tt> file and change the level to DEBUG or TRACE (instead of WARN): | ||
| Line 15: | Line 15: | ||
===Resolution=== | ===Resolution=== | ||
| − | The | + | The Web Services web application uses the Jetty root context. If other web applications served by the same instance of Jetty also use the root context, this can prevent the Web Services web application from getting routed requests. If you are working with a fresh install of Jetty, you should remove the default Jetty files from the <tt>$JETTY_HOME/webapps</tt> and <tt>$JETTY_HOME/contexts</tt> folders. |
[[Category:V:HTCC:8.5.2]] | [[Category:V:HTCC:8.5.2]] | ||
Revision as of 19:57, January 22, 2016
Troubleshooting
Contents
This page provides solutions to common problems in Web Services.
The following log for Web Services is saved to the /var/log/jetty directory on the Web Services node:
- cloud.log — Stores WARN level messages about Web Services.
To modify the log message levels, you can edit the $JETTY_HOME/resources/logback.xml file and change the level to DEBUG or TRACE (instead of WARN):
<logger name="com.genesyslab" level="DEBUG" />
404 Error
Problem
You receive a 404 Error on a diagnostic API request. For example, http://192.0.2.20:8080/api/v2/diagnostics/version.
Resolution
The Web Services web application uses the Jetty root context. If other web applications served by the same instance of Jetty also use the root context, this can prevent the Web Services web application from getting routed requests. If you are working with a fresh install of Jetty, you should remove the default Jetty files from the $JETTY_HOME/webapps and $JETTY_HOME/contexts folders.