The easiest fix is to reboot. If the problem persists, work through these steps
🔍 1. Port 9005 Already in Use
Aware IM uses port 9005 for the Tomcat shutdown port. If this port is already being used by another application, Tomcat can’t bind to it.
✅ Fix:
- Check for running processes using that port:
| Steps | Windows | MacOS Linux |
|---|
| First run | netstat -aon | findstr 9005 | lsof -i :9005 |
| Then run | taskkill /PID <pid> /F | kill -9 <pid> |
🔧 2. Another Aware IM or Java Process Is Running
Sometimes, AwareIM or Java processes don’t close cleanly.
✅ Fix:
- Check for existing Java or AwareIM processes and stop them.
- Rebooting your system can also clear stuck processes.
🛑 3. Firewall or Antivirus Blocking the Port
Security software may block traffic to or from port 9005.
✅ Fix:
- Allow port 9005 in your firewall or antivirus settings.
- Try disabling the antivirus temporarily and restart Aware IM.
⚙️ 4. Tomcat Misconfiguration
If server.xml in Aware IM’s Tomcat config is misconfigured, it may fail to bind to the port.
✅ Fix:
- Navigate to:
AwareIM/Tomcat/conf/server.xml
- Look for a line like this:
<Server port="9005" shutdown="SHUTDOWN">
- Change the port to another unused port (e.g., 9006), then restart.
🪲 5. Error in Logs
The Aware IM logs can give more detailed clues.
✅ Fix:
- Check these files:
- bin\logs\baserver.log
- Tomcat\logs\catalina.out or localhost.log
Look for anything mentioning port 9005, Address already in use, or BindException.
