You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Trustin Lee (JIRA)" <ji...@apache.org> on 2007/10/25 08:21:50 UTC

[jira] Commented: (DIRMINA-462) Thread.setName causes SecurityException in sandbox contexts (such as Applets)

    [ https://issues.apache.org/jira/browse/DIRMINA-462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12537510 ] 

Trustin Lee commented on DIRMINA-462:
-------------------------------------

And.. thanks for the patch! :)

> Thread.setName causes SecurityException in sandbox contexts (such as Applets)
> -----------------------------------------------------------------------------
>
>                 Key: DIRMINA-462
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-462
>             Project: MINA
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Andres Martinez Quijano
>            Assignee: Trustin Lee
>            Priority: Trivial
>             Fix For: 1.1.4, 1.0.7
>
>         Attachments: Thread.setName.patch.txt
>
>
> In several places (Executors and Connectors) it is called the method Thread.setName. 
> In an applet context this is forbidden by the sandbox, and a SecurityException arises.
> Provided is a patch that creates the class org.apache.mina.util.ThreadUtil which encapsulates the method call Thread.setName in a try/catch block and logs a warning if a SecurityException is thrown, and modifies all current calls to Thread.setName to use the ThreadUtil class

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.