Uploaded image for project: 'ModeShape'
  1. ModeShape
  2. MODE-1822

VersionManager.checkin throws exception in the transaction when using JTA transaction manager

    XMLWordPrintable

Description

    The following code will work with DummyTransacationManager but not real JTA transaction manager (Atomisk)

            @Transactional
        public void createNewNode(JCRSessionHolder sessionHolder) throws ItemExistsException, PathNotFoundException, NoSuchNodeTypeException, LockException, VersionException, ConstraintViolationException, RepositoryException {
            VersionManager vm = sessionHolder.getSession().getWorkspace().getVersionManager();

            Node node = sessionHolder.getSession().getRootNode().addNode("Test3", "pd:product");
            node.addMixin("mix:versionable");
            node.setProperty("name", "lalalal");
            node.setProperty("code", "lalalal");
            sessionHolder.getSession().save();
            vm.checkin(node.getPath());
        }

    Exception in thread "main" javax.jcr.InvalidItemStateException: This operation cannot be performed when the session has pending changes
    at org.modeshape.jcr.JcrVersionManager.checkin(JcrVersionManager.java:321)
    at org.modeshape.jcr.JcrVersionManager.checkin(JcrVersionManager.java:304)
    at JTATest$JCRTest.createNewNode(JTATest.java:76)
    at JTATest.main(JTATest.java:56)

    For VersionManager.checkout, if I call it in the beginning of the method and then make some change to the node, and save(), ModeShape will complain the node is not checkout.

    Attachments

      1. jprofiler_mode_1822.zip
        329 kB
      2. no-transaction.nps
        37 kB
      3. no-transaction.png
        no-transaction.png
        103 kB
      4. transaction.nps
        39 kB
      5. transaction.png
        transaction.png
        99 kB

      Issue Links

        incorporates

        Bug - A problem that impairs or prevents the functions of the product. MODE-1862 "java.lang.IllegalStateException: This is a tx cache!" when using federation

        • Critical - To be worked on immediately following BLOCKER issues.
        • Closed
        is related to

        Bug - A problem that impairs or prevents the functions of the product. MODE-1819 Session.move() fails when using user transactions

        • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
        • Closed

        Bug - A problem that impairs or prevents the functions of the product. MODE-1837 Sometimes query returns duplicated records after commiting a transaction that contains VersionManager.checkin() call when using a real JTA transaction manager

        • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
        • Closed
        relates to

        Bug - A problem that impairs or prevents the functions of the product. MODE-1854 Indexing took too much time to finish when using explicit JTA transaction compared to no transaction

        • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
        • Closed

        Activity

          People

            rhauch Randall Hauch (Inactive)
            ozhou_jira Oliver Zhou (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: