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

atlas-run-standalone --product confluence --version 5.5.2, Confluence won't start

      I am trying to build plugins for Confluence 5.5.2.

      I have atlassian-plugin-sdk-5.0.13, window 7 (64-bit) and JDK 1.7.0_45 (64-bit), here is my atlas-version output:
      ====begin===
      C:\Windows\System32>atlas-version

      ATLAS Version: 5.0.13
      ATLAS Home: C:\Users\rw5730\Documents\ATT\atlassian-plugin-sdk-5.0.13
      ATLAS Scripts: C:\Users\rw5730\Documents\ATT\atlassian-plugin-sdk-5.0.13\bin
      ATLAS Maven Home: C:\Users\rw5730\Documents\ATT\atlassian-plugin-sdk-5.0.13\apache-maven-3.2.1
      --------
      Executing: "C:\Users\rw5730\Documents\ATT\atlassian-plugin-sdk-5.0.13\apache-maven-3.2.1\bin\mvn.bat" --version -gs C:\Users\rw5730\Documents\ATT\atla
      ssian-plugin-sdk-5.0.13\apache-maven-3.2.1/conf/settings.xml
      Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9; 2014-02-14T09:37:52-08:00)
      Maven home: C:\Users\rw5730\Documents\ATT\atlassian-plugin-sdk-5.0.13\apache-maven-3.2.1\bin\..
      Java version: 1.7.0_45, vendor: Oracle Corporation
      Java home: C:\jdk\x64-jdk1.7.0_45\jre
      Default locale: en_US, platform encoding: Cp1252
      OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
      ===end===

      But then I ran the command:
      atlas-run-standalone --product confluence --version 5.5.2
      It the process look completed, because I saw these lines:
      ====begin===
      [INFO] [talledLocalContainer] Tomcat 6.x started on port [1990]
      [INFO] confluence started successfully in 129s at http://WACDTL03RW5730:1990/confluence
      [INFO] Type Ctrl-D to shutdown gracefully
      [INFO] Type Ctrl-C to exit
      ===end===

      But when I went to http://WACDTL03RW5730:1990/confluence in my browser, I saw:
      ====begin===
      type Exception report

      message java.lang.NullPointerException

      description The server encountered an internal error that prevented it from fulfilling this request.

      exception

      com.atlassian.util.concurrent.LazyReference$InitializationException: java.lang.NullPointerException
      com.atlassian.util.concurrent.LazyReference.getInterruptibly(LazyReference.java:149)
      com.atlassian.util.concurrent.LazyReference.get(LazyReference.java:112)
      com.atlassian.confluence.setup.ConfluenceEncodingFilter.getGlobalSettings(ConfluenceEncodingFilter.java:47)
      com.atlassian.confluence.setup.ConfluenceEncodingFilter.getEncodingInternal(ConfluenceEncodingFilter.java:37)
      com.atlassian.confluence.setup.ConfluenceEncodingFilter.getEncoding(ConfluenceEncodingFilter.java:29)
      com.atlassian.core.filters.encoding.AbstractEncodingFilter.doFilter(AbstractEncodingFilter.java:38)
      com.atlassian.core.filters.AbstractHttpFilter.doFilter(AbstractHttpFilter.java:31)
      com.atlassian.core.filters.HeaderSanitisingFilter.doFilter(HeaderSanitisingFilter.java:44)
      com.atlassian.confluence.servlet.FourOhFourErrorLoggingFilter.doFilter(FourOhFourErrorLoggingFilter.java:65)
      com.atlassian.confluence.web.filter.DebugFilter.doFilter(DebugFilter.java:50)
      com.atlassian.core.filters.AbstractHttpFilter.doFilter(AbstractHttpFilter.java:31)

      root cause

      java.lang.NullPointerException
      com.atlassian.spring.container.ContainerManager.getComponent(ContainerManager.java:33)
      com.atlassian.confluence.util.LazyComponentReference$Accessor.get(LazyComponentReference.java:46)
      com.atlassian.util.concurrent.Lazy$Strong.create(Lazy.java:85)
      com.atlassian.util.concurrent.LazyReference$Sync.run(LazyReference.java:321)
      com.atlassian.util.concurrent.LazyReference.getInterruptibly(LazyReference.java:143)
      com.atlassian.util.concurrent.LazyReference.get(LazyReference.java:112)
      com.atlassian.confluence.setup.ConfluenceEncodingFilter.getGlobalSettings(ConfluenceEncodingFilter.java:47)
      com.atlassian.confluence.setup.ConfluenceEncodingFilter.getEncodingInternal(ConfluenceEncodingFilter.java:37)
      com.atlassian.confluence.setup.ConfluenceEncodingFilter.getEncoding(ConfluenceEncodingFilter.java:29)
      com.atlassian.core.filters.encoding.AbstractEncodingFilter.doFilter(AbstractEncodingFilter.java:38)
      com.atlassian.core.filters.AbstractHttpFilter.doFilter(AbstractHttpFilter.java:31)
      com.atlassian.core.filters.HeaderSanitisingFilter.doFilter(HeaderSanitisingFilter.java:44)
      com.atlassian.confluence.servlet.FourOhFourErrorLoggingFilter.doFilter(FourOhFourErrorLoggingFilter.java:65)
      com.atlassian.confluence.web.filter.DebugFilter.doFilter(DebugFilter.java:50)
      com.atlassian.core.filters.AbstractHttpFilter.doFilter(AbstractHttpFilter.java:31)

      note The full stack trace of the root cause is available in the Apache Tomcat/6.0.41 logs.
      ===end===

      confluence-LATEST.log (attached) seems to complaint about database connection problems.

      However, I tried the command:
      atlas-run-standalone --product confluence
      and latest version of Confluence (5.6.6) started with no problem.

      So, how do I get
      atlas-run-standalone --product confluence --version 5.5.2
      to work properly?

      In addition, I just check the page: https://marketplace.atlassian.com/plugins/atlassian-plugin-sdk-windows/versions and it's listing Atlassian Plugin SDK 5.0.13 (the latest) only compatible up to Confluence version 5.4.4.? Should it support the latest version of Confluence 5.6.6? If so that page needs to be updated.

      Thanks.

        1. confluence-LATEST.log
          129 kB
          Royce Wong

            [CONFSERVER-36366] atlas-run-standalone --product confluence --version 5.5.2, Confluence won't start

            Atlassian Update - 10 April 2025

            Hi,

            At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products.

            This bug is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments; this inactivity suggests a low impact.

            Please note the comments on this thread are not being monitored.

            You can read more about our bug fix policy here and how we prioritize bugs.

            To learn more about our recent investments in Confluence Data Center, please check our public roadmap and dashboards containing recently resolved issues, current work, and future plans.

            Kind regards,
            Confluence Data Center

            George Varghese added a comment - Atlassian Update - 10 April 2025 Hi, At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products. This bug is being closed due to a lack of engagement in the last four years , including no new watchers, votes, or comments; this inactivity suggests a low impact. Please note the comments on this thread are not being monitored. You can read more about our bug fix policy here and how we prioritize bugs. To learn more about our recent investments in Confluence Data Center, please check our public roadmap and dashboards containing recently resolved issues , current work, and future plans . Kind regards, Confluence Data Center

            On the marketplace, it says that the Atlassian SDK is compatible with Confluence Server 2.0 - 5.4.4 (though obviously it supports 5.10), but I haven't had any luck running 5.5 or lower without downgrading the SDK. Should it even be possible to run Confluence 5.5 with the latest SDK? The two don't even support the same version of the JDK.

            Jason Boileau added a comment - On the marketplace, it says that the Atlassian SDK is compatible with Confluence Server 2.0 - 5.4.4 (though obviously it supports 5.10), but I haven't had any luck running 5.5 or lower without downgrading the SDK. Should it even be possible to run Confluence 5.5 with the latest SDK? The two don't even support the same version of the JDK.

            Hi Matthew,

            In this case, "mvn confluence:debug" is correct to run debug In your comment on 04/3/15 ?

            When I did it with "mvn amps:debug", it demands Oracle's jdbc driver.
            And Confluence wouldn't start even though install jdbc driver.

            Thanks,

            KURIMOTO Eiichi[Ricksoft] added a comment - - edited Hi Matthew, In this case, "mvn confluence:debug" is correct to run debug In your comment on 04/3/15 ? When I did it with "mvn amps:debug", it demands Oracle's jdbc driver. And Confluence wouldn't start even though install jdbc driver. Thanks,

            Having the same issue with atlas 5.0.13 and confluence 5.7.3, commenting as suggested by Stephen from Atlassian support.

            Meg Mitchell added a comment - Having the same issue with atlas 5.0.13 and confluence 5.7.3, commenting as suggested by Stephen from Atlassian support.

            Mukul added a comment -

            Facing the same issue with confluence version 5.5.4.

            Mukul added a comment - Facing the same issue with confluence version 5.5.4.

            Facing a similar issue here : https://answers.atlassian.com/questions/13417937/atlas-run-error-for-confluence-sdk-5.0.13

            Voting for this issue as suggested by Stephen Brannen

            Yagnesh Bhat added a comment - Facing a similar issue here : https://answers.atlassian.com/questions/13417937/atlas-run-error-for-confluence-sdk-5.0.13 Voting for this issue as suggested by Stephen Brannen

            Midori added a comment -

            Here are the properties generated for Hibernate in confluence.cfg.xml:

                <property name="hibernate.c3p0.acquire_increment">1</property>
                <property name="hibernate.c3p0.idle_test_period">100</property>
                <property name="hibernate.c3p0.max_size">30</property>
                <property name="hibernate.c3p0.max_statements">0</property>
                <property name="hibernate.c3p0.min_size">0</property>
                <property name="hibernate.c3p0.timeout">30</property>
                <property name="hibernate.connection.driver_class">org.hsqldb.jdbcDriver</property>
                <property name="hibernate.connection.isolation">2</property>
                <property name="hibernate.connection.password"></property>
                <property name="hibernate.connection.username">sa</property>
                <property name="hibernate.dialect">com.atlassian.hibernate.dialect.HSQL2Dialect</property>
                <property name="hibernate.setup">true</property>
            

            I think that the JDBC URL is missing?!! Should be the <property name="hibernate.connection.url">blablabla defined?

            Midori added a comment - Here are the properties generated for Hibernate in confluence.cfg.xml: <property name="hibernate.c3p0.acquire_increment">1</property> <property name="hibernate.c3p0.idle_test_period">100</property> <property name="hibernate.c3p0.max_size">30</property> <property name="hibernate.c3p0.max_statements">0</property> <property name="hibernate.c3p0.min_size">0</property> <property name="hibernate.c3p0.timeout">30</property> <property name="hibernate.connection.driver_class">org.hsqldb.jdbcDriver</property> <property name="hibernate.connection.isolation">2</property> <property name="hibernate.connection.password"></property> <property name="hibernate.connection.username">sa</property> <property name="hibernate.dialect">com.atlassian.hibernate.dialect.HSQL2Dialect</property> <property name="hibernate.setup">true</property> I think that the JDBC URL is missing?!! Should be the <property name="hibernate.connection.url">blablabla defined?

            Midori added a comment -

            I ran into the same problem with Confluence 5.5.6, and the root cause is:

            2015-03-04 15:04:49,702 WARN [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2] [mchange.v2.resourcepool.BasicResourcePool] run com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@7bde3bb0 -- Acquisition Attempt Failed!!! Clearing pending acquires. While trying to acquire a needed new resource, we failed to succeed more than the maximum number of allowed acquisition attempts (30). Last acquisition attempt exception: 
            java.lang.NullPointerException
                    at sun.jdbc.odbc.JdbcOdbcDriver.getProtocol(JdbcOdbcDriver.java:524)
                    at sun.jdbc.odbc.JdbcOdbcDriver.knownURL(JdbcOdbcDriver.java:493)
                    at sun.jdbc.odbc.JdbcOdbcDriver.acceptsURL(JdbcOdbcDriver.java:307)
                    at java.sql.DriverManager.getDriver(DriverManager.java:262)
                    at com.mchange.v2.c3p0.DriverManagerDataSource.driver(DriverManagerDataSource.java:223)
                    at com.mchange.v2.c3p0.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:134)
                    at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:182)
            

            Midori added a comment - I ran into the same problem with Confluence 5.5.6, and the root cause is: 2015-03-04 15:04:49,702 WARN [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2] [mchange.v2.resourcepool.BasicResourcePool] run com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask@7bde3bb0 -- Acquisition Attempt Failed!!! Clearing pending acquires. While trying to acquire a needed new resource, we failed to succeed more than the maximum number of allowed acquisition attempts (30). Last acquisition attempt exception: java.lang.NullPointerException at sun.jdbc.odbc.JdbcOdbcDriver.getProtocol(JdbcOdbcDriver.java:524) at sun.jdbc.odbc.JdbcOdbcDriver.knownURL(JdbcOdbcDriver.java:493) at sun.jdbc.odbc.JdbcOdbcDriver.acceptsURL(JdbcOdbcDriver.java:307) at java.sql.DriverManager.getDriver(DriverManager.java:262) at com.mchange.v2.c3p0.DriverManagerDataSource.driver(DriverManagerDataSource.java:223) at com.mchange.v2.c3p0.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:134) at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:182)

            Royce,

            Sorry to hear you're having problems with the sdk commands. While we investigate the issue, there may be a work around that will allow you to start writing your plugin.

            1. Create a plugin skeleton with the atlas-create-confluence-plugin command. This will create an empty plugin with some example implementations, which you can import in to your IDE.
            2. Edit the generated pom and set the confluence version to the version you wish to target the plugin, in this case I think that is 5.5.2.
            3. Inside the root directory of the plugin you just created, run this command:
            mvn amps:debug
            

            This will start up confluence with your skeleton plugin installed. Note that it will require you to have your own installation of maven for this to work.

            There is more details here: https://developer.atlassian.com/display/DOCS/Using+the+AMPS+Maven+Plugin+Directly

            Please let us know how this goes, and in the mean time we will talk to the sdk team and see if we can find the cause of the errors you're getting.

            Cheers
            Matt
            Confluence Developer Relations

            m@ (Inactive) added a comment - Royce, Sorry to hear you're having problems with the sdk commands. While we investigate the issue, there may be a work around that will allow you to start writing your plugin. Create a plugin skeleton with the atlas-create-confluence-plugin command. This will create an empty plugin with some example implementations, which you can import in to your IDE. Edit the generated pom and set the confluence version to the version you wish to target the plugin, in this case I think that is 5.5.2. Inside the root directory of the plugin you just created, run this command: mvn amps:debug This will start up confluence with your skeleton plugin installed. Note that it will require you to have your own installation of maven for this to work. There is more details here: https://developer.atlassian.com/display/DOCS/Using+the+AMPS+Maven+Plugin+Directly Please let us know how this goes, and in the mean time we will talk to the sdk team and see if we can find the cause of the errors you're getting. Cheers Matt Confluence Developer Relations

              Unassigned Unassigned
              9b354c0e923f Royce Wong
              Affected customers:
              8 This affects my team
              Watchers:
              15 Start watching this issue

                Created:
                Updated:
                Resolved: