You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Robert Stupp (JIRA)" <ji...@apache.org> on 2016/01/19 22:18:40 UTC

[jira] [Commented] (CASSANDRA-11033) Prevent logging in sandboxed state

    [ https://issues.apache.org/jira/browse/CASSANDRA-11033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15107455#comment-15107455 ] 

Robert Stupp commented on CASSANDRA-11033:
------------------------------------------

As a workaround it should work to set {{scan="false"}} in {{logbook.xml}}: {{<configuration scan="false">}}

> Prevent logging in sandboxed state
> ----------------------------------
>
>                 Key: CASSANDRA-11033
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11033
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Robert Stupp
>            Assignee: Robert Stupp
>            Priority: Minor
>             Fix For: 3.0.x
>
>
> logback will re-read its configuration file regularly. So it is possible that logback tries to reload the configuration while we log from a sandboxed UDF, which will fail due to the restricted access privileges for UDFs. UDAs are also affected as these use UDFs.
> /cc [~doanduyhai]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)