JBoss EAP 6.1+部署启动异常及相关告警问题咨询

Hey there, let’s work through these three JBoss deployment headaches you’re facing—they’re all solvable with a few targeted checks and fixes!

1. Server Fails to Start When Projects Exist in deploy Folder #

Error: Server JBoss EAP 6.1+ Runtime Server failed to start

Here’s how to diagnose and fix this:

• Verify deployment file integrity: Corrupted EAR/WAR files are a common culprit. Use the jar command to check if the file structure is intact:

  jar tf my-ear-7.5.13.ear
  

  If you see missing files or corrupted entries, re-package the application and try again.
• Clean temporary and cache directories: JBoss stores cached deployment data that can get corrupted. Stop the server first, then delete the contents of:
  • JBOSS_HOME/standalone/tmp (for standalone mode)
  • JBOSS_HOME/standalone/data (for standalone mode)
    For domain mode, target JBOSS_HOME/domain/tmp and JBOSS_HOME/domain/data instead. Restart the server after cleaning.
• Dig into detailed server logs: The generic "failed to start" message doesn’t tell the whole story. Check JBOSS_HOME/standalone/log/server.log for specific exceptions—look for missing dependencies, invalid configuration files (like persistence.xml or jboss-web.xml), or classpath conflicts.

2. Warning: JBAS015000: Cannot delete deployment progress marker file #

This warning usually stems from file locks or permission issues:

• Manually clean deployment markers: Stop the server, then delete any marker files in the deploy directory (these end with extensions like .dodeploy, .isdeploying, .deployed). Also clear the corresponding content in JBOSS_HOME/standalone/data/content.
• Check directory permissions: Ensure the user running JBoss has read/write access to the deploy, tmp, and data directories. On Linux, you can adjust permissions with:

  chown -R jboss_user:jboss_group JBOSS_HOME/standalone
  

• Release IDE file locks: If you’re deploying from an IDE (like Eclipse), the IDE might be holding locks on deployment files. Restart the IDE and try deploying again.

3. Message: JBAS018559: Deployed "my-ear-7.5.13.ear" (runtime-name : "my-ear-7.5.13.ear") + Timestamp #

Good news—this isn’t an error at all! It’s a success log confirming that your EAR file was deployed successfully to the server. The timestamp is just when the log entry was recorded. As long as there are no accompanying errors or warnings, your application should be up and running.

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