[LUCENE-670] improper isolation (overuse of system properties) allows Lucene apps to clobber each other

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

Environment

Tomcat

• Assignee: Unassigned
• Reporter: Ken Geis
• Created: 08/Sep/06 00:31
• Updated: 28/Aug/22 11:30
• Resolved: 08/Sep/06 17:31

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

• is part of: LUCENE-636 [PATCH] Differently configured Lucene 'instances' in same JVM