How To Resolve Tomcat - Openfire Port Conflict
By Angsuman Chakraborty, Gaea News NetworkTuesday, November 13, 2007
Openfire (Jabber/XMPP server) by default binds on port 8080 which is also used by Tomcat. This causes Tomcat to fail when openfire is started before it. The solution, as always, is simple.
You can either change the port of Openfire or Tomcat. Alternatively you can bind them on different IP addresses in machines with multiple interfaces or use 127.0.0.1 for one and the IP address associated with the ethernet card for another. Here are the steps to change the port (simplest solution):
How to change Openfire default http port (8080)
1. To configure openfire browse to https://localhost:9090/.
2. Login with the password you had previously provided.
Note: Look here to recover openfire admin password.
3. Click on Http Binding to either disable it or use a different port like 7070.
4. Now stop and start openfire (openfire/bin/openfire stop && openfire/bin/openfire start) to use the new port.
How to change Tomcat default port (8080)
1. Open server.xml and search for a line starting with: <Connector port="8080" maxHttpHeaderSize=…
2. Change the port value (default 8080) to a port number of your choice
3. Restart tomcat (/sbin/service tomcat5 restart).
I prefer changing the port of Openfire.
Notes:
1. Tomcat is reference implementation of Servlet & JSP specification and is one of the most popular JSP & Servlet container
2. Openfire is a popular Jabber (XMPP protocol) server (Openfire usage notes).
Tags: Jabber, JSP, Servlet, Tomcat
March 13, 2008: 8:23 am
Openfire may still conflict with tomcat after disabling/moving the administration console. ..to continue the above fix: Click on “http binding” under “server settings” ..This affects both 8080 and 8483, which may both conflict with tomcat. |
Brian