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

Unable to create a Confluence Space when a default space logo is configured - Page not found after the Create Space button is clicked

      NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.

      After the last upgrade from 5.1-OD-13 to 5.2-OD-3 on July 8, 2013, some OnDemand Confluence instances cannot create new Spaces.

      Clicking the 'Create Space' button should bring you to the newly created Space homepage, however the Space and page are never created, resulting in a 'page not found' error.

      The following message appears in the log:

      2013-07-08 10:09:26.847030500 2013-07-08 10:09:26,844 ERROR [TP-Processor2] [persistence.dao.hibernate.HibernateSpaceDao] getSpace Found a bad space id in the space id cache : [ 11010049 ] for [key ] which returned this: null. Removing this id from the cache now.
      

      However no other error appears (even with debug logging enabled).

      Workaround

      Turn off the default space logo in Confluence Admin -> Default Space Logo (the URL should be https://example.atlassian.net/wiki/admin/configuredefaultspacelogo.action). This will allow spaces to be created.

            [CONFSERVER-29865] Unable to create a Confluence Space when a default space logo is configured - Page not found after the Create Space button is clicked

            Please update your documentation. For server site the URL is actually: https://<Base URL>/admin/configuredefaultspacelogo.action

            Rachel Richardson added a comment - Please update your documentation. For server site the URL is actually:  https://<Base URL>/admin/configuredefaultspacelogo.action

            @tpretorius as it stands currently, the fix can not be rolled out before the 29th of July, as the bug affects a core library of the product and the fix unfortunately missed the release train for the 22nd of July

            As reported before, the bug manifest with an error like

            Page Not Found
            The page you were trying to reach could not be found. This could be because:
            The page does not exist.
            The page exists, but you do not have permission to view it.
            Site Search
            

            The reason for this misleading message is that the a (nested) transaction got silently rolled back, leading to the new Space not getting persisted in the database. However, the code is unaware of this, and caches the generated Space id. This leads to running through the default success route, which discovers the cached Space id but can not retrieve any data for it. Thus the only thing that appears on the system logs is

            2013-07-08 09:42:02.829656500 2013-07-08 09:42:02,826 ERROR [TP-Processor18] [persistence.dao.hibernate.HibernateSpaceDao] getSpace Found a bad space id in the space id cache : [ 62226437 ] for [test ] which returned this: null. Removing this id from the cache now.
            

            As written above, the faulty code is part of the core product. Please continue with the workaround of (temporarily) disabling the default Space logo for now. I will update this issue once the fix is rolled out in OnDemand.

            fabs (Inactive) added a comment - @ tpretorius as it stands currently, the fix can not be rolled out before the 29th of July, as the bug affects a core library of the product and the fix unfortunately missed the release train for the 22nd of July As reported before, the bug manifest with an error like Page Not Found The page you were trying to reach could not be found. This could be because: The page does not exist. The page exists, but you do not have permission to view it. Site Search The reason for this misleading message is that the a (nested) transaction got silently rolled back, leading to the new Space not getting persisted in the database. However, the code is unaware of this, and caches the generated Space id. This leads to running through the default success route, which discovers the cached Space id but can not retrieve any data for it. Thus the only thing that appears on the system logs is 2013-07-08 09:42:02.829656500 2013-07-08 09:42:02,826 ERROR [TP-Processor18] [persistence.dao.hibernate.HibernateSpaceDao] getSpace Found a bad space id in the space id cache : [ 62226437 ] for [test ] which returned this : null . Removing this id from the cache now. As written above, the faulty code is part of the core product. Please continue with the workaround of (temporarily) disabling the default Space logo for now. I will update this issue once the fix is rolled out in OnDemand.

            Novohit added a comment -

            Thanks @David Nicholson, I reset to default space logo and turned it off, now I can create spaces. Thanks!

            Novohit added a comment - Thanks @David Nicholson, I reset to default space logo and turned it off, now I can create spaces. Thanks!

            Hi david36, please try removing the space logo per the Workaround referenced in the details of this ticket. If that is not successful for you, please file a ticket at https://support.atlassian.com and support will assist you.

            Thanks,
            -dave

            David Nicholson (Inactive) added a comment - Hi david36 , please try removing the space logo per the Workaround referenced in the details of this ticket. If that is not successful for you, please file a ticket at https://support.atlassian.com and support will assist you. Thanks, -dave

            Novohit added a comment -

            I have the same issue reported by Florent Ferere, after creating a space, I'm redirected to the space's URL but the content is this (see text bellow), plus, the space is not created on the spacelist.

            Page Not Found
            The page you were trying to reach could not be found. This could be because:
            The page does not exist.
            The page exists, but you do not have permission to view it.
            Site Search

            Go to
            Site Homepage
            Your Dashboard

            Please help

            Novohit added a comment - I have the same issue reported by Florent Ferere, after creating a space, I'm redirected to the space's URL but the content is this (see text bellow), plus, the space is not created on the spacelist. Page Not Found The page you were trying to reach could not be found. This could be because: The page does not exist. The page exists, but you do not have permission to view it. Site Search Go to Site Homepage Your Dashboard Please help

            T added a comment - - edited

            When will this fix be released?

            T added a comment - - edited When will this fix be released?

            Having default space logo on also prevents you from changing the space Home Page.

            Richard Lin added a comment - Having default space logo on also prevents you from changing the space Home Page.

            As others have observed, disabling the default space logo, adding the space and then turning the default logo back on worked to get my space added.

            Karl Burkum added a comment - As others have observed, disabling the default space logo, adding the space and then turning the default logo back on worked to get my space added.

            Removing and disabling the default space logo worked for us too.

            Florent Ferere (DO NOT USE) added a comment - Removing and disabling the default space logo worked for us too.

            The workaround of disabling the default space logo worked for me.

            Jonathan Hult added a comment - The workaround of disabling the default space logo worked for me.

              fakraemer fabs (Inactive)
              imaduro Ivan Maduro (Inactive)
              Affected customers:
              11 This affects my team
              Watchers:
              59 Start watching this issue

                Created:
                Updated:
                Resolved: