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

Problems with defining node types in clustered environment with eviction enabled

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • 3.1.0.Final
    • 3.0.1.Final
    • Clustering
    • None
    • Hide

      Start up two clustered instances of Modeshape with .CND defined node types. When the two instances communicate, an NPE is thrown on the first instance and the second instance gets a failed transaction since the sync failed between the two instances.

      Show
      Start up two clustered instances of Modeshape with .CND defined node types. When the two instances communicate, an NPE is thrown on the first instance and the second instance gets a failed transaction since the sync failed between the two instances.
    • Workaround Exists
    • Hide

      One workaround appears to be to not use eviction. This is not ideal, since that means that the Infinispan cache attempts to keep all nodes in-memory. However, it may be a practical workaround for smaller repositories.

      Show
      One workaround appears to be to not use eviction. This is not ideal, since that means that the Infinispan cache attempts to keep all nodes in-memory. However, it may be a practical workaround for smaller repositories.

    Description

      We are having a problem running ModeShape in a clustered environment. The issue arises when we attempt to define custom node types (via a .cnd file) in our .json repository configuration file. The first instance of Modeshape comes up fine. The problem is when the second instance comes up. We get a stack trace containing an NPE on both instances. This happens every time at startup. When we remove the reference to the .cnd file from the repository .json file, everything starts up properly.

      This may to be related to MODE-1703, which appears to have been fixed back about 24 days ago, but we are still seeing a problem. Any help on this would be greatly appreciated. We are evaluating ModeShape as our repository of choice, and this is currently a blocker for us.

      Attachments

        1. build.output.zip
          71 kB
        2. firstInstance.log
          22 kB
        3. modeshape.zip
          17 kB
        4. repository1.json
          0.9 kB
        5. repository2.json
          0.9 kB
        6. repository-infinispan-test1.xml
          4 kB
        7. repository-infinispan-test2.xml
          4 kB
        8. repository-test.cnd
          0.2 kB
        9. secondInstance.log
          56 kB

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. MODE-1739 Data corruption when starting up another cluster instance

          • 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. ISPN-2095 Eviction causes lost AtomicMap entries

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

          Bug - A problem that impairs or prevents the functions of the product. ISPN-2903 Manual eviction should not delete entry from cache store

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

          Activity

            People

              rhauch Randall Hauch (Inactive)
              rickcole3_jira Rick Cole (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: