[jira] [Resolved] (TOREE-421) KernelSecurityManager doesn't allow users to create their own thread groups
[ https://issues.apache.org/jira/browse/TOREE-421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luciano Resende resolved TOREE-421. --- Fix Version/s: 0.4.0 Assignee: Kevin Bates Resolution: Fixed > KernelSecurityManager doesn't allow users to create their own thread groups > --- > > Key: TOREE-421 > URL: https://issues.apache.org/jira/browse/TOREE-421 > Project: TOREE > Issue Type: Bug >Reporter: Piyush Narang >Assignee: Kevin Bates >Priority: Major > Fix For: 0.4.0 > > > I'm trying to run a Spark Scala job using Toree and I'm running into some > issues as the code in our job calls into one of our libraries which tries to > create threads in its own ThreadGroup: > https://github.com/twitter/util/blob/develop/util-core/src/main/scala/com/twitter/concurrent/NamedPoolThreadFactory.scala#L28 > This seems to cause this check in Toree's KernelSecurityManager to trip: > https://github.com/apache/incubator-toree/blob/master/kernel-api/src/main/scala/org/apache/toree/security/KernelSecurityManager.scala#L121 > Stack looks like: > {code} > Name: java.lang.SecurityException > Message: Not allowed to modify ThreadGroups! > StackTrace: at > org.apache.toree.security.KernelSecurityManager.checkAccess(KernelSecurityManager.scala:114) > at java.lang.ThreadGroup.checkAccess(ThreadGroup.java:315) > at java.lang.Thread.init(Thread.java:394) > at java.lang.Thread.init(Thread.java:349) > at java.lang.Thread.(Thread.java:599) > at > com.twitter.concurrent.NamedPoolThreadFactory.newThread(NamedPoolThreadFactory.scala:32) > ... > {code} > Here's a simple repro: > {code} > println(Thread.currentThread().getThreadGroup) // default thread group > val group: ThreadGroup = new > ThreadGroup(Thread.currentThread().getThreadGroup(), "name") > val hello = new Thread(group, new Runnable { > def run() { > println("hello world") > } > }) > println(hello.getThreadGroup) > hello.start > {code} > Any suggestions for working around this? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (TOREE-421) KernelSecurityManager doesn't allow users to create their own thread groups
[ https://issues.apache.org/jira/browse/TOREE-421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16965037#comment-16965037 ] ASF GitHub Bot commented on TOREE-421: -- lresende commented on pull request #178: [TOREE-421] Allow thread groups URL: https://github.com/apache/incubator-toree/pull/178 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > KernelSecurityManager doesn't allow users to create their own thread groups > --- > > Key: TOREE-421 > URL: https://issues.apache.org/jira/browse/TOREE-421 > Project: TOREE > Issue Type: Bug >Reporter: Piyush Narang >Priority: Major > > I'm trying to run a Spark Scala job using Toree and I'm running into some > issues as the code in our job calls into one of our libraries which tries to > create threads in its own ThreadGroup: > https://github.com/twitter/util/blob/develop/util-core/src/main/scala/com/twitter/concurrent/NamedPoolThreadFactory.scala#L28 > This seems to cause this check in Toree's KernelSecurityManager to trip: > https://github.com/apache/incubator-toree/blob/master/kernel-api/src/main/scala/org/apache/toree/security/KernelSecurityManager.scala#L121 > Stack looks like: > {code} > Name: java.lang.SecurityException > Message: Not allowed to modify ThreadGroups! > StackTrace: at > org.apache.toree.security.KernelSecurityManager.checkAccess(KernelSecurityManager.scala:114) > at java.lang.ThreadGroup.checkAccess(ThreadGroup.java:315) > at java.lang.Thread.init(Thread.java:394) > at java.lang.Thread.init(Thread.java:349) > at java.lang.Thread.(Thread.java:599) > at > com.twitter.concurrent.NamedPoolThreadFactory.newThread(NamedPoolThreadFactory.scala:32) > ... > {code} > Here's a simple repro: > {code} > println(Thread.currentThread().getThreadGroup) // default thread group > val group: ThreadGroup = new > ThreadGroup(Thread.currentThread().getThreadGroup(), "name") > val hello = new Thread(group, new Runnable { > def run() { > println("hello world") > } > }) > println(hello.getThreadGroup) > hello.start > {code} > Any suggestions for working around this? -- This message was sent by Atlassian Jira (v8.3.4#803005)
Podling Toree Report Reminder - November 2019
Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 20 November 2019, 10:30 am PDT. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted 2 weeks before the board meeting, to allow sufficient time for review and submission (Wed, November 06). Please submit your report with sufficient time to allow the Incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. Candidate names should not be made public before people are actually elected, so please do not include the names of potential committers or PPMC members in your report. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. * How does the podling rate their own maturity. This should be appended to the Incubator Wiki page at: https://cwiki.apache.org/confluence/display/INCUBATOR/November2019 Note: This is manually populated. You may need to wait a little before this page is created from a template. Note: The format of the report has changed to use markdown. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC