-
Bug
-
Resolution: Cannot Reproduce
-
Low
-
None
-
5.4.3, 5.5.6, 5.8.6, 5.8.10, 5.10.6, 5.10.7, 6.3.4, 6.13.1
-
69
-
Severity 3 - Minor
-
4
-
NOTE: This bug report is for Confluence Server. Using Confluence Cloud? 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.
- relates to
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
[CONFSERVER-14040] FindSingleObject Uh oh - found more than one object when single object requested - globaldescription
We have found a lot of these duplicate attachments and tracked it down to when we have updated from 7.4.8 to 7.4.10. Since then until now (7.13.4 DC) we are experiencing duplicates created each day.
Please check and resolve.
Thanks and regards,
Robert
I have used this for analyzing further details of the defect in our oracle db.
select * from content c where c.contenttype = 'ATTACHMENT' and c.content_status = 'current' and c.prevver is null and exists (select * from content i where c.contentid <> i.contentid and c.contenttype = i.contenttype and c.title = i.title and c.version = i.version and c.creator = i.creator and c.creationdate = i.creationdate and c.lastmodifier = i.lastmodifier and c.lastmoddate = i.lastmoddate and c.content_status = i.content_status and c.spaceid = i.spaceid and c.pageid = i.pageid and c.hibernateversion = i.hibernateversion and c.lowertitle = i.lowertitle) order by 1, 2, 3 asc;
2020-02-06 12:46:20,346 ERROR [http-nio-8090-exec-24] [core.persistence.hibernate.HibernateObjectDao] findSingleObject Uh oh - found more than one object when single object requested: [Attachment: Test.png v.1 (101580883) iucroitoru, Attachment: Test.png v.1 (101580889) iucroitoru]
– url: /pages/viewpage.action | page: 98893901 | traceId: 3199cf98cc14ba4f | userName: iucroitoru | referer: https://uatconfluence.endava.com/pages/viewpage.action?pageId=98893901 | action: viewpage
2020-02-06 12:46:24,833 ERROR [http-nio-8090-exec-13] [core.persistence.hibernate.HibernateObjectDao] findSingleObject Uh oh - found more than one object when single object requested: [Attachment: Test.png v.1 (101580883) iucroitoru, Attachment: Test.png v.1 (101580889) iucroitoru]
We experience the same issue on 7.2.2 Server
Hans-Peter Geier
added a comment - this issue does not even have an assignee! Quite unacceptable! We are facing the same issue on version 6.3.4 for more than 200 pages. That must be fixed soon, especially as this bug is nearly 10 years old !
Any update on this?
Same issue here with Gliffy diagrams
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.
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.
Hi All,
A quick update on this one.
We've attempted to reproduce this issue with the steps provided by the community and have been unable to do so. Unfortunately the issue here describes a symptom rather than the issue itself, and whilst we know this condition can occur, this doesn't give us anything to actually fix.
As such we're going to close the issue. If you're able to reliably reproduce this issue, please contact support via https://support.atlassian.com with reproduction steps so we can investigate further.
Closing the ticket.
Thanks,
James Ponting
Engineering Manager - Confluence Data Center