[jira] [Created] (STANBOL-863) SolrYard needs to access SolrServer using AccessController.doPrivileged

["Rupert Westenthaler (JIRA)" <ji...@apache.org>]

Rupert Westenthaler created STANBOL-863:
-------------------------------------------

             Summary: SolrYard needs to access SolrServer using AccessController.doPrivileged
                 Key: STANBOL-863
                 URL: https://issues.apache.org/jira/browse/STANBOL-863
             Project: Stanbol
          Issue Type: Bug
          Components: Entityhub
            Reporter: Rupert Westenthaler
            Assignee: Rupert Westenthaler
            Priority: Critical


The access of Apache Solr to Files in the solr instanceDir is not permitted by the SecurityManager given the permissions of the anonymous user. This results in exceptions such as

    Caused by: java.security.AccessControlException: access denied (java.io.FilePermission
    {stanbol-working-dir}/stanbol/indexes/default/entityhub-2012.12.22/data/index.propertiesread)
        at java.security.AccessControlContext.checkPermission(AccessControlContext.java:374)
        [..]
        at java.io.File.exists(File.java:731)
        at org.apache.solr.core.SolrCore.getNewIndexDir(SolrCore.java:197)

Typically this appears when adding Documents to the SolrServer. Therefore users will see those Exceptions on calls to store(..), update(..) or remove(..). However internally those exceptions do also appear when storing the namespace prefix map to the SolrServer.

User facing Exceptions will look like 

    Caused by: org.apache.stanbol.entityhub.servicesapi.yard.YardException:
    Exception while adding Document to Solr
        at org.apache.stanbol.entityhub.yard.solr.impl.SolrYard.store(SolrYard.java:1170)

resulting in HTTP responses with status 500




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira