[
https://issues.apache.org/jira/browse/LUCENE-5471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13912089#comment-13912089
]
Uwe Schindler commented on LUCENE-5471:
---------------------------------------
I thought about that, too. Question is: What privilege is needed to do this?
The problem is: depending on the ClassLoader we may see some stuff, others not.
Has to do with the crazy codebase attribute in the policy file. You may only
see some specific JAR files or only some java packages. So mostly impossible to
get the real reason, without the code down in the ClassLoader hierarchy
throwing a SecurityEx. I think we should keep it as it is. Maybe document it,
that you need permissions to "see" the JAR files and resources in it.
> Classloader issues when running Lucene under a java SecurityManager
> -------------------------------------------------------------------
>
> Key: LUCENE-5471
> URL: https://issues.apache.org/jira/browse/LUCENE-5471
> Project: Lucene - Core
> Issue Type: Bug
> Affects Versions: 4.5
> Reporter: Rick Hillegas
> Attachments: SecureLucene.java
>
>
> I see the following error when I run Lucene 4.5.0 under a java
> SecurityManager. I will attach a test program which shows this problem. The
> program works fine when a SecurityManager is not installed. But the program
> fails when I install a SecurityManager. Even more puzzling, the program works
> if I first run it without a SecurityManager, then install a SecurityManager,
> then re-run the program, all within the lifetime of a single JVM. I would
> appreciate advice about how to work around this problem:
> Exception in thread "main" java.lang.ExceptionInInitializerError
> at
> org.apache.lucene.index.LiveIndexWriterConfig.<init>(LiveIndexWriterConfig.java:122)
> at
> org.apache.lucene.index.IndexWriterConfig.<init>(IndexWriterConfig.java:165)
> at SecureLucene$1.run(SecureLucene.java:129)
> at SecureLucene$1.run(SecureLucene.java:122)
> at java.security.AccessController.doPrivileged(Native Method)
> at SecureLucene.getIndexWriter(SecureLucene.java:120)
> at SecureLucene.runTest(SecureLucene.java:72)
> at SecureLucene.main(SecureLucene.java:52)
> Caused by: java.lang.IllegalArgumentException: A SPI class of type
> org.apache.lucene.codecs.Codec with name 'Lucene45' does not exist. You need
> to add the corresponding JAR file supporting this SPI to your classpath.The
> current classpath supports the following names: []
> at org.apache.lucene.util.NamedSPILoader.lookup(NamedSPILoader.java:109)
> at org.apache.lucene.codecs.Codec.forName(Codec.java:95)
> at org.apache.lucene.codecs.Codec.<clinit>(Codec.java:122)
> ... 8 more
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
