-
Type:
Bug
-
Resolution: Duplicate
-
Priority:
Medium
-
None
-
Affects Version/s: 2.10
-
Component/s: None
Seem on extranet :
atl-extranet-conf-cluster=> select * from content where title = 'Performance Management Project' and version =3 order by version; contentid | contenttype | title | body | version | creator | creationdate | lastmodifier | lastmoddate | prevver | spaceid | parentid | blogspaceid | descspaceid | pageid | username | content_status | mailspaceid | messageid | parentcommentid | versioncomment | draftpageid | draftspacekey | drafttype | draftpageversion | child_position ------------+-------------+--------------------------------+------+---------+---------+-------------------------+--------------+-------------------------+------------+-------------------+----------+-------------+-------------+--------+----------+----------------+-------------+-----------+-----------------+----------------+-------------+---------------+-----------+------------------+---------------- 1682376541 | PAGE | Performance Management Project | | 3 | jluijke | 2008-10-23 21:40:15.108 | jluijke | 2008-10-23 21:44:21.643 | | 69512637731700803 | | | | | | deleted | | | | | | | | | 1682608570 | PAGE | Performance Management Project | | 3 | jluijke | 2008-10-23 21:45:45.787 | jluijke | 2008-10-23 21:52:51.845 | 1682376555 | | | | | | | current |
It would appear that if there are ever two concurrent calls to
public void save(EntityObject objectToSave, EntityObject previousVersion)
in VersionedHibernateObjectDao with the same previousVersion, duplicate page versions could be created.
This is somewhat unlikely, as generally each call to save should have a new previousVersion, but it is possible if the initial transaction were to be delayed.
- duplicates
-
-
- Closed
-
- relates to
-
-
- Closed
-