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

["Trustin Lee (JIRA)" <ji...@apache.org>]

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

Trustin Lee resolved DIRMINA-462.
---------------------------------

       Resolution: Fixed
    Fix Version/s: 1.0.7
                   1.1.4
         Assignee: Trustin Lee

Fixed.  Instead of introducing ThreadUtil, I modified NamePreservingRunnable which is widely used by I/O workers.  All setName() calls are now handled by NamePreservingRunnable, and therefore NamePreservingRunnable takes care of the raised exceptions now.  Please confirm this bug is fixed and close this issue.

> 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.