Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-17549

Confluence 3-1 beta1 fails to start if JIRA 4.0 is also running in Tomcat

      Hi everyone. When I try to start JIRA 4.0 and Confluence 3.1 together in Tomcat 6.0.20 the startup fails. I already adressed the issue in this support request: JSP-45714 But answer was that milestone releases are not supported. Now I thought because we use this config and Confluence is now beta I should create a bug report.

      Error is something like: FelixStartLevel ERROR

      See attached log!

            [CONFSERVER-17549] Confluence 3-1 beta1 fails to start if JIRA 4.0 is also running in Tomcat

            This only fixes the problem in case Confluence starts first.

            In case JIRA starts first you still need to patch JIRA as described in the knowledge base entry. The issue is tracked as JRA-19894.

            Chris Kiehl added a comment - This only fixes the problem in case Confluence starts first. In case JIRA starts first you still need to patch JIRA as described in the knowledge base entry . The issue is tracked as JRA-19894 .

            This is the related Atlassian Plugins issue: https://studio.atlassian.com/browse/PLUG-493

            Chris Kiehl added a comment - This is the related Atlassian Plugins issue: https://studio.atlassian.com/browse/PLUG-493

            Yes, it works. Looking forward the fix in Confluence 3.1.1 because I can't tell our customers to start ajira and not jira .

            Michael Michael added a comment - Yes, it works. Looking forward the fix in Confluence 3.1.1 because I can't tell our customers to start ajira and not jira .

            After some additional testing, Jira and Confluence both work if jira is started before confluence. We did this by renaming the jira.xml file to ajira.xml. This isn't a suggested solution but it shows that the problem occurs when Felix 2.0.2 is loaded before Felix 1.2.1 but not the other way around.

            Brian Nguyen (Inactive) added a comment - After some additional testing, Jira and Confluence both work if jira is started before confluence. We did this by renaming the jira.xml file to ajira.xml. This isn't a suggested solution but it shows that the problem occurs when Felix 2.0.2 is loaded before Felix 1.2.1 but not the other way around.

            Brian has confirmed that Jira 4.0 does work with Conf 3.0.2

            Mark Hrynczak (Inactive) added a comment - - edited Brian has confirmed that Jira 4.0 does work with Conf 3.0.2

            Mark, can you check if this is specific to Confluence 3.1, or if it has been like this even before? Our assumption is that Jira 4 should not have worked even with Confluence 2.10 and 3.0, but we should have a look.

            Per Fragemann [Atlassian] added a comment - Mark, can you check if this is specific to Confluence 3.1, or if it has been like this even before? Our assumption is that Jira 4 should not have worked even with Confluence 2.10 and 3.0, but we should have a look.

            I think it is too late for a fix in 3.1, but we must work on this asap, possibly next week already, so it is ready for 3.1.1 whenever that comes out. We will need to make this clear in the release notes and upgrade notes. Creating a documentation issue.

            Per Fragemann [Atlassian] added a comment - I think it is too late for a fix in 3.1, but we must work on this asap, possibly next week already, so it is ready for 3.1.1 whenever that comes out. We will need to make this clear in the release notes and upgrade notes. Creating a documentation issue.

            Thanks for paying attention on this! I reported the problem weeks ago, but was told milestone builds are not supportet (JSP-45714). Thanks a lot for fixing it now because we exactly run this Tomcat configuration.

            Michael Michael added a comment - Thanks for paying attention on this! I reported the problem weeks ago, but was told milestone builds are not supportet (JSP-45714). Thanks a lot for fixing it now because we exactly run this Tomcat configuration.

            I've managed to reproduce the problem running the same configuration. A note for possible future support cases, Jira will start correctly after the initial configuration and the problem only occurs after Tomcat is restarted. The problem is caused by faulty url handling in the Felix framework.

            In order to fix this, both Jira and Confluence will need to upgrade their Felix dependency to 2.0.2. There is a possibility that only upgrading Confluence 3.1 will fix the problem but it is unlikely.

            Given late stage of Confluence 3.1's development cycle and the unlikelihood of fixing the problem completely, the current thinking is that upgrading Felix is a "nice to have" for 3.1 but a must have for 3.1.1 and 3.2.

            In the meantime, our recommendation is that Confluence and Jira should not be deployed in the same Tomcat container.

            Brian Nguyen (Inactive) added a comment - I've managed to reproduce the problem running the same configuration. A note for possible future support cases, Jira will start correctly after the initial configuration and the problem only occurs after Tomcat is restarted. The problem is caused by faulty url handling in the Felix framework. In order to fix this, both Jira and Confluence will need to upgrade their Felix dependency to 2.0.2. There is a possibility that only upgrading Confluence 3.1 will fix the problem but it is unlikely. Given late stage of Confluence 3.1's development cycle and the unlikelihood of fixing the problem completely, the current thinking is that upgrading Felix is a "nice to have" for 3.1 but a must have for 3.1.1 and 3.2. In the meantime, our recommendation is that Confluence and Jira should not be deployed in the same Tomcat container.

              ckiehl Chris Kiehl
              9168e3332326 Michael Michael
              Affected customers:
              0 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: