Jump to: navigation, search

Difference between revisions of "Jetty/Troubleshooting"

(Saving)
Line 1: Line 1:
 
{{Jetty FAQ Section}}  
 
{{Jetty FAQ Section}}  
 +
 +
== Big Problems ==
 +
 +
 +
{{Jetty FAQ
 +
| question = Why won't Jetty Start?
 +
| answer =
 +
}}
 +
 +
{{Jetty FAQ
 +
| question = Why isn't my application/servlet/content served?
 +
| answer =
 +
}}
 +
 +
{{Jetty FAQ
 +
| question = Jetty has locked up?
 +
| answer =
 +
}}
 +
 +
{{Jetty FAQ
 +
| question = Jetty is using 100% CPU?
 +
| answer =
 +
}}
 +
 +
 +
 +
  
 
== Saving  ==
 
== Saving  ==

Revision as of 20:56, 23 March 2011



Big Problems

Question Mark.png Why won't Jetty Start?


Question Mark.png Why isn't my application/servlet/content served?


Question Mark.png Jetty has locked up?


Question Mark.png Jetty is using 100% CPU?



Saving

Question Mark.png Why do I get a "Save could not be completed" error in Eclipse whenever I try to save a file while Jetty is running?

This is a limitation of Windows -- having a file open in one process means that you can't write to that same file with another process. Since Jetty has mapped the file to its cache, which prevents the file from being edited, you'll need to turn off caching to work around the problem. You can turn off caching in the default servlet by setting <useFileMappedBuffer> to false in webdefault.xml.