Lucene - Core
  1. Lucene - Core
  2. LUCENE-670

improper isolation (overuse of system properties) allows Lucene apps to clobber each other

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Critical Critical
    • Resolution: Duplicate
    • Affects Version/s: 1.9, 2.0.0
    • Fix Version/s: None
    • Component/s: core/index, core/store
    • Labels:
      None
    • Environment:

      Tomcat

      Description

      As nicely stated by the Javadoc for org.apache.commons.discovery.tools.ManagedProperties, "System properties are global in nature, so using them easily violates sound architectural and design principles for maintaining separation between components and runtime environments." Lucene's use of system properties makes it so that one web application that uses Lucene can break another web application that uses Lucene.

      Both org.apache.lucene.index.SegmentReader and org.apache.lucene.store.FSDirectory use system properties to locate an implementation class. Because of this, two applications can step on each others' toes.

      So, I have two webapps running in Tomcat. One uses the Compass Framework which sets the SegmentReader implementation class to org.apache.lucene.index.CompassSegmentReader. My other webapp tries to initialize SegmentReader in a different classloader, and it fails with an ExceptionInInitializerError because it can't load that class. If I get lucky, the non-Compass webapp loads first and things run smoothly.

        Issue Links

          Activity

          Hide
          Hoss Man added a comment -

          This appears to be the same issue as LUCENE-636.

          Ken: if you could take a look at that issue (and the associated patch), and indicate wether it addresses your concerns (in which case this issue should be marked a dup) or not (in which case please clarify what other problems you see not already described/addressed by that issue.

          feel free to vote for LUCENE-636 as well to raise it's visibility.

          Show
          Hoss Man added a comment - This appears to be the same issue as LUCENE-636 . Ken: if you could take a look at that issue (and the associated patch), and indicate wether it addresses your concerns (in which case this issue should be marked a dup) or not (in which case please clarify what other problems you see not already described/addressed by that issue. feel free to vote for LUCENE-636 as well to raise it's visibility.
          Hide
          Ken Geis added a comment -

          I guess I didn't search well enough for a previously submitted bug.

          LUCENE-636 addresses my concerns and the patch is coded very close to how I had it in my head.

          Please mark this as a duplicate of LUCENE-636. (It doesn't appear that I have permission to do so.)

          Show
          Ken Geis added a comment - I guess I didn't search well enough for a previously submitted bug. LUCENE-636 addresses my concerns and the patch is coded very close to how I had it in my head. Please mark this as a duplicate of LUCENE-636 . (It doesn't appear that I have permission to do so.)

            People

            • Assignee:
              Unassigned
              Reporter:
              Ken Geis
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development