I’m having trouble with my local development environment where I have both JIRA and Confluence installed. JIRA runs on port 8080 while Confluence uses port 8090. They both connect to separate databases on the same MySQL server running on port 3306.
The main issue is that when one service starts, it causes the other to lose connection
Here’s what happens step by step: I can login to Confluence without problems and everything works normally like creating new spaces and content. But as soon as I launch the JIRA service, my Confluence session gets terminated automatically. When I try to access Confluence again, I can’t login anymore. However, JIRA becomes accessible at that point. The same behavior occurs if I reverse the order and start JIRA first.
Has anyone encountered this kind of conflict before? What could be causing this mutual interference between the two Atlassian products?
definitely check your max_connections in MySQL, if it’s low, that would cause disconnection issues. Also, make sure JIRA and Confluence are not using the same schema - that’s a recipe for chaos! good luck!
Had the exact same issue running multiple Atlassian apps locally. Session management conflicts were killing me - JIRA and Confluence kept writing session data to the same temp directory, so they’d constantly invalidate each other’s sessions. Check your server.xml files and make sure each installation has different work directories. Also double-check that your context paths don’t overlap and each app has unique session cookie names. Worth looking at your JVM parameters too - any shared system properties can mess things up at the server level.
Sounds like a database connection pool issue. I ran into this when both apps had overlapping pool settings that maxed out MySQL’s available connections. Check your JIRA and Confluence connection pools - they’re probably grabbing too many connections together. Also verify your MySQL user accounts have the right permissions and aren’t hitting per-user connection limits. Worth checking if there’s any shared cache configs or temp file locations causing conflicts between the instances too.