I’m having trouble with my local setup where I have both JIRA and Confluence running on the same machine. JIRA is configured to use port 8080 while Confluence runs on port 8090. Both applications connect to separate databases that are hosted on a single MySQL server running on the default port 3306.
Main Issue
Whenever I launch one service, the other one loses its connection and stops working properly.
What happens exactly: When I access Confluence first, everything works normally and I can manage my content without problems. But as soon as I start the JIRA service, my Confluence session gets terminated automatically. If I try to log back into Confluence, it doesn’t work, but JIRA becomes accessible. The same behavior occurs if I reverse the order and start JIRA first.
Has anyone experienced this kind of conflict before? What could be causing this mutual interference between the two services?
This sounds like a database connection pool issue, not a port conflict. Both JIRA and Confluence are probably fighting over database connections - one grabs them all when it starts up, leaving the other high and dry. Check your MySQL max_connections setting and make sure it can handle both apps running together. I ran into the same thing when my MySQL was capped at 100 connections but each app was trying to use 80 connections in their pools. You should also check if both apps are using different database users with their own connection limits - that way they can’t starve each other out.
Had the same issue - turned out to be licensing, not technical. Both apps were using the same server ID or MAC address for license validation, so Atlassian’s system saw them as conflicting instances. When one would authenticate, it’d kill the other’s session. Check your server.xml files and make sure each app has a unique server ID. Also double-check that your licenses are set up right for your server configuration. This drove me nuts for weeks before I figured out the license conflict was killing sessions, not some connectivity issue.
totally! both apps can be real resource hogs. def check your memory limits and consider staggering their startup times. also, your db may be getting overloaded, so keep an eye on its performance too!