JBOSS EAP 7.2域默认服务器无法启动（CentOS 7）求助

架构老林

2026-5-14

Hey there, let’s troubleshoot why your JBoss EAP 7.2 managed servers (server-one, server-two, server-three) won’t start on your CentOS 7 server—even though the domain controller fires up fine. Since this works locally, we can focus on environment-specific issues on your server. Here’s what to check step by step:

Fix File/Directory Permissions
CentOS is strict about permissions, and running JBoss as root or having incorrect ownership on the JBoss directory is a common culprit.
- First, avoid starting JBoss with the root user—this causes permission conflicts for managed server processes later. Create a dedicated jboss user if you haven’t already.
- Set proper ownership on your JBoss EAP directory:
```
chown -R jboss:jboss /path/to/your/jboss-eap-7.2
chmod -R 750 /path/to/your/jboss-eap-7.2
```
Check for Port Conflicts
It’s likely another process on your CentOS server is using the ports your managed servers need. By default:
- server-one uses 8080, server-two uses 8180, server-three uses 8280
- Managed servers also communicate with the domain controller on port 9999
- Run this command to check for occupied ports:
```
netstat -tulpn | grep -E '8080|8180|8280|9999'
```
- If you find a conflict, edit domain/configuration/domain.xml to adjust the port-offset for the affected server (e.g., set port-offset="300" for server-three if 8280 is taken) or stop the conflicting process.
Tweak Java Memory Settings
Your CentOS server might have less available RAM than your local machine, causing the managed servers to run out of memory on startup.
- Open the domain configuration file:
```
vi domain/bin/domain.conf
```
- Adjust the JAVA_OPTS to lower the heap size (example for a server with 4GB total RAM):
```
JAVA_OPTS="-Xms512m -Xmx1024m -XX:MaxMetaspaceSize=256m ..."
```
- Save the file, restart the domain controller, and try starting the managed servers again.
Disable SELinux Temporarily (Then Fix Properly)
SELinux in enforcing mode can block JBoss from binding ports or writing to files.
- Test by temporarily turning it off:
```
setenforce 0
```
- If the servers start after this, configure SELinux to allow JBoss to run permanently:
  1. Install the policy tools:
```
yum install policycoreutils-python
```
  2. Allow JBoss to bind its HTTP ports:
```
semanage port -a -t http_port_t -p tcp 8080
semanage port -a -t http_port_t -p tcp 8180
semanage port -a -t http_port_t -p tcp 8280
```
  3. Give JBoss write access to its directory:
```
chcon -R -t httpd_sys_content_rw_t /path/to/your/jboss-eap-7.2
```
  4. Re-enable SELinux:
```
setenforce 1
```

Check Firewall Rules
The CentOS firewall might be blocking communication between the domain controller and managed servers.

Test by stopping the firewall temporarily:
```
systemctl stop firewalld
```

If this fixes the issue, add permanent rules to allow JBoss traffic:

firewall-cmd --add-port=9990/tcp --permanent  # Domain controller admin port
firewall-cmd --add-port=9999/tcp --permanent  # Managed server communication
firewall-cmd --add-port=8080-8280/tcp --permanent  # HTTP ports
firewall-cmd --reload

Restart the firewall afterward:
```
systemctl start firewalld
```

Compare Configs with Your Local Setup
It’s possible your server’s JBoss config files were modified accidentally.
- Back up your server’s domain/configuration/domain.xml and host.xml, then copy the working versions from your local machine to the server.
- Restart the domain controller and try starting the managed servers again.
Dig Into the Server Logs
If none of the above works, check the managed server logs for specific error messages—they’ll tell you exactly what’s failing.
- Logs are located at domain/servers/server-one/log/server.log (replace server-one with the other server names to check their logs). Look for keywords like Permission denied, Address already in use, or OutOfMemoryError to pinpoint the issue.

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