Tomcat Troubleshootings
Last modified by Eleni Cojocariu on 2026/05/28 16:07
Content
Explanation
When installing XWiki using the war package and configuring Tomcat as a servlet container, there are several common warnings, errors, and configuration issues that administrators may encounter. For example:
- A generic Tomcat startup failure indicating that XWiki failed to initialize correctly: "Severe: Error listenerStart" in Logs.
- Error indicating that the operating system cannot allocate additional threads for Tomcat: "Unable to Create Native Thread" Errors on Debian Systems.
- Headless mode configuration issues.
- Large XWiki forms, Page edits, or extension operations may exceed Tomcat's default request parameter limits: Parameter Count Exceeded Allowed Maximum
- Large authentication headers, cookies, or reverse proxy headers may exceed Tomcat defaults: Request Header is Too Large
- Old serialized sessions may become incompatible and trigger deserialization errors during startup: Session Deserialization Errors in Tomcat
- Tomcat may report warnings about ThreadLocal objects not being properly released when XWiki shuts down or is redeployed: ThreadLocal Memory Leak Warnings on Shutdown
More
To find more about the current topic, you can search or use the table below and filter the columns to narrow your choices.