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

Data corruption when starting up another cluster instance

    XMLWordPrintable

Details

    Description

      When I run a Modeshape cluster with two instances, where I first start one instance and begin populating it, then start another instance and access the nodes being created on the first instance, eventually the system gets into an inconsistent state.

      Attachments

        1. jetty_18080_1356002900.log
          68 kB
        2. jetty_18081_1356002900.log
          20 kB
        3. pp-modeshape.zip
          225 kB
        4. pp-modeshape-2.zip
          17 kB
        5. pp-modeshape-3.zip
          14 kB

        Issue Links

          is blocked by

          Bug - A problem that impairs or prevents the functions of the product. MODE-1746 Deadlock when writing same nodes in different order using separate threads

          • 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
          is related to

          Bug - A problem that impairs or prevents the functions of the product. MODE-1754 ModeShape 3.1 cannot use Infinispan 5.2.0.CR1 in a clustered environment when eviction is enabled.

          • 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
          relates to

          Bug - A problem that impairs or prevents the functions of the product. MODE-1733 Problems with defining node types in clustered environment with eviction enabled

          • 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

          Bug - A problem that impairs or prevents the functions of the product. MODE-1745 NullPointerException while running ModeShape embedded in spring with TransactionManager in clustered mode

          • 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

          Activity

            People

              rhauch Randall Hauch (Inactive)
              patno Patrik Nordebo (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: