Tomcat突然无法部署：生产环境Web应用异常及日志分析

Hey there, let's walk through the issues in your logs and figure out why your web app went down.

First: Fix the MaxPermSize Warning #

The first line in your log is a straightforward warning:

Java HotSpot(TM) Client VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0

Here's the scoop: Java 8 completely eliminated the Permanent Generation (PermGen) space and replaced it with Metaspace. That old MaxPermSize parameter does nothing now—the JVM just ignores it. To fix this (and ensure proper memory management):

• Open your Tomcat startup config file: either bin/catalina.sh (Linux/macOS) or bin/catalina.bat (Windows)
• Locate where MaxPermSize=256m is set (usually in CATALINA_OPTS or JAVA_OPTS environment variables)
• Replace it with -XX:MaxMetaspaceSize=256m (this caps Metaspace usage like you intended for PermGen; if you don't need a hard limit, you can just remove the parameter entirely—Metaspace defaults to using available system memory)
• Save the file and restart Tomcat, and the warning will vanish.

Next: Diagnose Why Your Web App Stopped #

Your log cuts off at Initialization processed i...—we're missing the critical part where Tomcat either finished starting, hit a fatal error, or crashed. To get to the root cause:

• Check the full content of catalina.out: Scroll past the truncated section to look for ERROR level logs or exception stack traces (these are usually marked with SEVERE in Tomcat logs)
• Dig into other Tomcat log files in the logs/ folder:
  • localhost.log: Tracks server-specific events, often including app initialization failures
  • localhost_access_log.*.txt: Logs incoming requests—if the app crashed mid-run, you might see a spike in errors right before it stopped
  • manager.log (if you use the Tomcat Manager): Could hold clues about deployment issues
• Common red flags to watch for:
  • OutOfMemoryError (either in Metaspace or the main heap—adjust -Xmx/-Xms heap parameters if this happens)
  • Class not found errors (indicates missing dependencies)
  • Failed database connections (check if your DB was down or credentials changed)
  • Invalid configuration files (like broken web.xml or Spring Boot settings)

Quick Pro Tips #

• If you're running Tomcat on Java 8+, always audit your JVM parameters to avoid outdated flags like MaxPermSize
• Set up log rotation for catalina.out so it doesn't grow too large and truncate critical info
• Use tools like jstat or jconsole to monitor JVM memory usage proactively, before crashes occur

内容的提问来源于stack exchange，提问作者Michael