F2F | Documentation | Soft-exceptions
If the hard code detects an abnormal state, it throws soft exceptions, each of which has a unique code, listed in soft-exceptions.xml. Roughly speaking, the larger the code, the worse the problem. Codes of 8000 or over correspond to a <f2f:fatal-error> which halts server execution. Error codes of 8000 or more indicate an F2F server bug. If you can reproduce them, please report them.
| Code | Level | Explanation |
| 1xxx | Server Notice | FYI |
| 2xxx | Daemon Notice | FYI |
| 3xxx | Server Warning | May not be a problem (e.g. File/process not found) |
| 5xxx | Server Error | Badly formed soft code. |
| 6xxx | Communication error | Interoperation with bad software, either a broken client or a broken F2F server elsewhere. |
| 7xxx | Server Error | Understood causes. You really should work out what is causing these errors, but they are non-fatal so the soft-server can ignore them. |
| 79xx | Unrecoverable Server Error | Understood causes (e.g. deletion of files, disk full etc.) |
| 8xxx | Daemon error | Buggy processes managing server input/output. |
| 9xxx | Server Error | Buggy server code. Recoverable, so if you need to ignore them (at the risk of corrupting your data!) you can set up the server to do so. |
| 99xx | Fatal Server Error | Buggy server code. These errors are the most important to report. |
Generated 2009-07-16 07:34:58 Europe/London from a docbook.xml by F2F Documentation Module.