Uploaded image for project: 'Confluence Cloud'
  1. Confluence Cloud
  2. CONFCLOUD-14040

FindSingleObject Uh oh - found more than one object when single object requested - globaldescription

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

      This error appears in the logs when there's two items in the database:

      2008-12-20 18:17:23,697 ERROR [http-8080-Processor4] [com.atlassian.hibernate.HibernateObjectDao] findSingleObject Uh oh - found more than one object when single object requested: [globaldescription: v.1 (29687809), globaldescription: v.1 (29687810)]
      – url: /login.action | userName: anonymous

      The workaround is to delete one of the duplicate rows from the Content table, with ContentID being the value in parentheses.

            [CONFCLOUD-14040] FindSingleObject Uh oh - found more than one object when single object requested - globaldescription

            Hi everyone,

            Thank you for previously raising this bug and bringing it to our attention.

            Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Confluence users.

            As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.

            Thank you again for providing valuable feedback to our team!

            Sunny Xu (Inactive) added a comment - Hi everyone, Thank you for previously raising this bug and bringing it to our attention. Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Confluence users. As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know. Thank you again for providing valuable feedback to our team!

            Any update on this?

            Same issue here with Gliffy diagrams

            Jens Kasperek (Bosch GmbH) added a comment - Any update on this? Same issue here with Gliffy diagrams

            Same issue on 5.10.7

            Michal Sladek added a comment - Same issue on 5.10.7

            Same issue on 5.9.6

            Michal Sladek added a comment - Same issue on 5.9.6

            It looks like this can impact notifications as well:

            atlassian-confluence.log.5:2016-08-29 07:50:33,664 ERROR [http-nio-8090-exec-501] [com.atlassian.hibernate.HibernateObjectDao] findSingleObject Uh oh - found more than one object when single object requested: [com.atlassian.confluence.mail.notification.Notification@5bf8439, com.atlassian.confluence.mail.notification.Notification@5bf843a] 
            

            Since they are in memory, there is no way to recover from this situation without loosing emails.

            Boris Berenberg [Uber] added a comment - It looks like this can impact notifications as well: atlassian-confluence.log.5:2016-08-29 07:50:33,664 ERROR [http-nio-8090-exec-501] [com.atlassian.hibernate.HibernateObjectDao] findSingleObject Uh oh - found more than one object when single object requested: [com.atlassian.confluence.mail.notification.Notification@5bf8439, com.atlassian.confluence.mail.notification.Notification@5bf843a]  Since they are in memory, there is no way to recover from this situation without loosing emails.

            An easy way to solve an uh oh error is to delete one the two attachments via the user interface:

            • Search on the attachment name you see in the logs
            • Go to the page containing the attachment
            • Go to the attachments
            • Sort by name and verify the attachment is there twice
            • delete one of them (this should have no impact on your page)

            Of course, you have to to this one by one, so if you have hundreds of double attachments, it may take a while to do this

            Kristof Vandermeersch added a comment - An easy way to solve an uh oh error is to delete one the two attachments via the user interface: Search on the attachment name you see in the logs Go to the page containing the attachment Go to the attachments Sort by name and verify the attachment is there twice delete one of them (this should have no impact on your page) Of course, you have to to this one by one, so if you have hundreds of double attachments, it may take a while to do this

            Steps to reproduce

            1. Upload attachment to page.
            2. Upload attachment to page again
            3. Look to DB
              # select spaceid, pageid, title, version, lastmoddate, content_status from content 
              where contenttype='ATTACHMENT' and title='4AA1-7850ENW-datasheet.pdf' order by lastmoddate;
               spaceid |  pageid   |           title            | version |       lastmoddate       | content_status
              ---------+-----------+----------------------------+---------+-------------------------+----------------
                    38 | 126156803 | 4AA1-7850ENW-datasheet.pdf |       1 | 2016-05-18 15:51:02.148 | current
                    38 | 126156803 | 4AA1-7850ENW-datasheet.pdf |       2 | 2016-05-18 15:51:29.152 | current
              
            4. Delete attachment in Attachments area
            5. Look to DB - only last version is deleted
                    38 | 126156803 | 4AA1-7850ENW-datasheet.pdf |       1 | 2016-05-18 15:51:02.148 | current
                    38 | 126156803 | 4AA1-7850ENW-datasheet.pdf |       2 | 2016-05-18 15:51:29.152 | deleted
              
            6. Upload attachment again - uh oh
                    38 | 126156803 | 4AA1-7850ENW-datasheet.pdf |       1 | 2016-05-18 15:51:02.148 | current
                    38 | 126156803 | 4AA1-7850ENW-datasheet.pdf |       2 | 2016-05-18 15:51:29.152 | deleted
                    38 | 126156803 | 4AA1-7850ENW-datasheet.pdf |       1 | 2016-05-18 15:53:18.876 | current
              

            Jozef Kotlár added a comment - Steps to reproduce Upload attachment to page. Upload attachment to page again Look to DB # select spaceid, pageid, title, version, lastmoddate, content_status from content where contenttype='ATTACHMENT' and title='4AA1-7850ENW-datasheet.pdf' order by lastmoddate; spaceid | pageid | title | version | lastmoddate | content_status ---------+-----------+----------------------------+---------+-------------------------+---------------- 38 | 126156803 | 4AA1-7850ENW-datasheet.pdf | 1 | 2016-05-18 15:51:02.148 | current 38 | 126156803 | 4AA1-7850ENW-datasheet.pdf | 2 | 2016-05-18 15:51:29.152 | current Delete attachment in Attachments area Look to DB - only last version is deleted 38 | 126156803 | 4AA1-7850ENW-datasheet.pdf | 1 | 2016-05-18 15:51:02.148 | current 38 | 126156803 | 4AA1-7850ENW-datasheet.pdf | 2 | 2016-05-18 15:51:29.152 | deleted Upload attachment again - uh oh 38 | 126156803 | 4AA1-7850ENW-datasheet.pdf | 1 | 2016-05-18 15:51:02.148 | current 38 | 126156803 | 4AA1-7850ENW-datasheet.pdf | 2 | 2016-05-18 15:51:29.152 | deleted 38 | 126156803 | 4AA1-7850ENW-datasheet.pdf | 1 | 2016-05-18 15:53:18.876 | current

            same issue for 5.8.x and 5.9.x

            Hans-Peter Geier added a comment - same issue for 5.8.x and 5.9.x

            This issue is now open for 7 years. See: https://jira.atlassian.com/browse/CONF-13480

            Are there any plans to work on this issue?

            Isn't there any workaround to prevent confluence from creating duplicate entries?

            Jens Kasperek (Bosch GmbH) added a comment - This issue is now open for 7 years . See: https://jira.atlassian.com/browse/CONF-13480 Are there any plans to work on this issue? Isn't there any workaround to prevent confluence from creating duplicate entries?

            Same for 5.7.6

            Intel CHD Jira Admin added a comment - Same for 5.7.6

              Unassigned Unassigned
              jlargman Jeremy Largman
              Affected customers:
              36 This affects my team
              Watchers:
              38 Start watching this issue

                Created:
                Updated:
                Resolved: