Details

      Description

      The lockForChildInsertRemove flag gets propagated to all nodes but the root. The root node is being constructed at least four times, three of which properly extract this flag from Configuration object; the remaining one doesn't because it receives null Configuration (it's the first one created). The thing is that the object returned as the root node to the application is the only one with this flag uninitialized.

      At this point I saw the stack trace and gave up all hopes of penetrating the initialization logic

      Usually this is no big deal, but I have a test that can reliably blow up in 10 seconds on average (on an old, UP laptop) because of that and it scares me...

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                manik Manik Surtani
                Reporter:
                ksobolew Krzysztof Sobolewski
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: